New Dart Editor Build 5104

[Eric Clayberg]

New Dart Editor build available...

http://gsdview.appspot.com/dart-editor-archive-integration/latest/

Highlights ... build 5104

• New Files view replaces old Libraries view
• Switch to perform analysis agaisnt Dart SDK runtime libraries
• Cleaned up wizards, welcome page, and UI to reflect switch to new Files view
• Improved launch configurations
• Analysis engine (DartC) improvements and cleanup
• Modified "native" keyword analysis to support usage in Frog

Full change log ...

http://gsdview.appspot.com/dart-editor-archive-integration/latest/changelog.html

Tutorial ...

http://www.dartlang.org/docs/getting-started/editor/

[Matt B]

Looking great so far, Will play with it more tonight. Though the 'open
folders' as opposed to a file will take some getting used to.

One thing I've noticed already:
All of my calls to print() from within a class are showing a warning
that 'Print is not a method in <className>' (where classname is
whatever class the statement appears in).

Keep up the great work guys!
Matt

On Mar 7, 4:11 pm, Eric Clayberg <clayb...@google.com> wrote:
> New Dart Editor build available...
>
> http://gsdview.appspot.com/dart-editor-archive-integration/latest/
>
> Highlights ... build 5104
>

>    - New Files view replaces old Libraries view
>    - Switch to perform analysis agaisnt Dart SDK runtime libraries
>    - Cleaned up wizards, welcome page, and UI to reflect switch to new
>    Files view
>    - Improved launch configurations
>    - Analysis engine (DartC) improvements and cleanup
>    - Modified "native" keyword analysis to support usage in Frog
>
>  Full change log ...
>
> http://gsdview.appspot.com/dart-editor-archive-integration/latest/cha...
>
> Tutorial ...
>
> http://www.dartlang.org/docs/getting-started/editor/

[Robert Beeger]

I also noticed that the unittesting framework I copied from the dart sources from client/testing is marked with some errors like "cannot resolve window" and "Native keyword can be used only in corelib".

I can launch my tests like before though. So it doesn't seem to bother Dart VM or Frog.

I prefer the files interface over the libraries interface. Thanks for that.

But I also miss being able to simply browse the dart libraries. Since it is no libraries view, the used dart libraries aren't shown like they were before. 

So I'd like to have back the libraries view back as an addition to look at the used libraries.

Cheers,

  Robert

[Phil Quitslund]

Hey Matt,

A few comments inline:

Looking great so far, Will play with it more tonight. Though the 'open
folders' as opposed to a file will take some getting used to.

Right.  It is a change.  Hopefully the new resource and navigation model will ultimately feel more natural to you...  If not, it'd be good to hear your thoughts!

 

One thing I've noticed already:
All of my calls to print() from within a class are showing a warning
that 'Print is not a method in <className>' (where classname is
whatever class the statement appears in).

We're working on this.  In the short term, adding 

#import('dart:builtin');

should at least make those squiggles go away....

Keep up the great work guys!

Thanks!  And keep the feedback coming!

 

-phil

On Mar 7, 4:11 pm, Eric Clayberg <clayb...@google.com> wrote:
> New Dart Editor build available...
>
> http://gsdview.appspot.com/dart-editor-archive-integration/latest/
>
> Highlights ... build 5104
>

>    - New Files view replaces old Libraries view
>    - Switch to perform analysis agaisnt Dart SDK runtime libraries
>    - Cleaned up wizards, welcome page, and UI to reflect switch to new
>    Files view
>    - Improved launch configurations
>    - Analysis engine (DartC) improvements and cleanup
>    - Modified "native" keyword analysis to support usage in Frog
>
>  Full change log ...
>
> http://gsdview.appspot.com/dart-editor-archive-integration/latest/cha...
>
> Tutorial ...
>
> http://www.dartlang.org/docs/getting-started/editor/

--
Phil Quitslund

Software Engineer

Google, Inc.

[Ross Smith]

Hi guys,

Are there any steps required to bring an existing project into this
build?

When I do 'File->Open Folder...' on my application nothing appears in
the Files view, but I see this Exception thrown in the logs:

S: Windows 7 - amd64 (6.1)
SDK installed = true
Dartium installed = false
////////////////////////////////////////////////////////////////////////////////////
!SESSION 2012-03-07 19:45:02.334
-----------------------------------------------
eclipse.buildId=unknown
java.version=1.6.0_18
java.vendor=Sun Microsystems Inc.
BootLoader constants: OS=win32, ARCH=x86_64, WS=win32, NL=en_CA
Command-line arguments: -os win32 -ws win32 -arch x86_64 -data
workspace

!ENTRY org.eclipse.ui.workbench 4 0 2012-03-07 19:45:34.590
!MESSAGE An unexpected exception was thrown.
!STACK 0
java.net.URISyntaxException: Illegal character in opaque part at index
2: C:\myharddrive\isasecret
at java.net.URI$Parser.fail(Unknown Source)
at java.net.URI$Parser.checkChars(Unknown Source)
at java.net.URI$Parser.parse(Unknown Source)
at java.net.URI.<init>(Unknown Source)
at java.net.URI.create(Unknown Source)
at
com.google.dart.tools.ui.actions.OpenExternalFolderDialogAction.run(OpenExternalFolderDialogAction.java:
70)
at
com.google.dart.tools.ui.internal.handlers.OpenFolderHandler.execute(OpenFolderHandler.java:
53)
at
org.eclipse.ui.internal.handlers.HandlerProxy.execute(HandlerProxy.java:
293)
at org.eclipse.core.commands.Command.executeWithChecks(Command.java:
476)
at
org.eclipse.core.commands.ParameterizedCommand.executeWithChecks(ParameterizedCommand.java:
508)

[Phil Quitslund]

Hey Ross!

That looks like a bug in our URI creation -- URI.create(..) is the culprit.  The good news is that it should be fixed in a recent continuous build.  If you're daring, grab a recent build and retry.  Otherwise, we'll be pushing out a fresh integration build end of week.

Thanks!

-phil

[Ross Smith]

hey Phil,

I dare! That bug does seem to be fixed now, I can now load my
application into the files view. When I go to launch I get a new
error, but I see that I also get it with Sunflower:

# Getting file path from: file:///C:/dart/dart-sdk/lib/frog/frogc.dart
# Path: /C:/dart/dart-sdk/lib/frog/frogc.dart
Unable to open file: /C:/dart/dart-sdk/lib/frog/frogc.dart
Failure to launch - unable to generate JavaScript for sunflower.html.

Looks like that leading '/' on the path might be the culprit this
time. I'll wait a bit for the dust to settle :)

thanks,
-Ross

On Mar 7, 7:56 pm, Phil Quitslund <pquitsl...@google.com> wrote:
> Hey Ross!
>
> That looks like a bug in our URI creation -- URI.create(..) is the culprit.
>  The good news is that it should be fixed in a recent continuous build.  If
> you're daring, grab a recent build and retry.  Otherwise, we'll be pushing
> out a fresh integration build end of week.
>
> Thanks!
>
> -phil
>

[Phil Quitslund]

Thanks for pushing on this Ross.

I opened an issue for your latest snag: http://code.google.com/p/dart/issues/detail?id=2056

We'll take a look tomorrow.

-phil

[Chris Buckett]

>    - New Files view replaces old Libraries view

Will the old Libraries view still be available in the future? I quite
liked the ability to browse through imported libraries.

Thanks
Chris.

[Gen]

I might prefer this solution:
- Give a checkbox to show or hide the files and their folders not
linked by #import and #source.
- Display a different icon for linked .dart files and folders and
those that are not.
Maybe use a bold text font for the linked files and folders or a
different text color for those that are not linked like grey or
yellow. Or blue for those that are linked.

Concerning the Files view, I miss a "copy file" and "copy folder"
option.
But so far I am very happy with the Files view and its features.
I have not (yet) missed the Libraries view because it made the Editor
hardly usable for me; I have used a generic text editor for now.

[Phil Quitslund]

On Thu, Mar 8, 2012 at 1:09 PM, Gen <gp78...@gmail.com> wrote:

I might prefer this solution:
- Give a checkbox to show or hide the files and their folders not
linked by #import and #source.
- Display a different icon for linked .dart files and folders and
those that are not.
 Maybe use a bold text font for the linked files and folders or a
different text color for those that are not linked like grey or
yellow. Or blue for those that are linked.

Great input.  Stay tuned for an update real soon on this front.

 

Concerning the Files view, I miss a "copy file" and "copy folder"
option.

We're on it: http://code.google.com/p/dart/issues/detail?id=2066

 

But so far I am very happy with the Files view and its features.
I have not (yet) missed the Libraries view because it made the Editor
hardly usable for me; I have used a generic text editor for now.

Good to hear. If you we lose you to a text editor again, do let us know why!

 

Thanks for the feedback!

-phil

On 8 Mrz., 20:19, Chris Buckett <chrisbuck...@gmail.com> wrote:
> >    - New Files view replaces old Libraries view
>
> Will the old Libraries view still be available in the future? I quite
> liked the ability to browse through imported libraries.
>
> Thanks
> Chris.

[Daniel Rubel]

The new Files view is a good step forward IMO, but now we need to improve browsing libraries and discoverability. Reviving the Libraries view with some changes is one of the several possible directions we are discussing.

[Phil Quitslund]

We're working on something.  Out of curiosity, are you keen to browse just imported libraries or (your) user-defined ones as well?

Thanks for chiming in!

-phil

[Gen]

> > I have not (yet) missed the Libraries view because it made the Editor
> > hardly usable for me; I have used a generic text editor for now.
>
> Good to hear. If you we lose you to a text editor again, do let us know why!

The reasons for not using the Editor were:
1)
The libraries view was fragile when I used it.
This means that it crashed frequently when I changed files and folders
behind the scenes.
I had to restart the Editor each time in order to have the Ediitor's
benefits compared to a generic text editor.

2)
I am just starting a project.
Hence I change file, folders and class names frequently.
But no file and folder manipulations were available except for
creating a file (and folders ?).
And files disappeared when they are not longer linked.

3)
Furthermore:
- There is not yet any auto formatting of code.
- Tabs are converted into space chars. I like my tabs.
- The auto completion is not yet that helpful as I need to know the
semantics of the new Dart libraries API too.
Hence I have to check the API web page anyway.

On 8 Mrz., 22:25, Phil Quitslund <pquitsl...@google.com> wrote:

[Jim Hugunin]

I am very happy to have the new files view.  Thanks!

However, I noticed that I am now missing the ability to browse imported libraries that are somewhere else in my filesystem.  dart:core and dart:dom are the two most obvious cases.  I notice this most obviously when I use "Go to declaration" on something like String.  The editor very nicely brings up the appropriate file for me - but the file doesn't have any directory context and I feel a little bit at sea that I can't go looking for the other things in the same library.

I'm not quite sure how I'd like to see this - but I recall that eclipse did a tolerable job of handling this for pure Java code?

I really like the fact that every week the editor gets more pleasant to use.  Just last week I set a breakpoint in my dart code, ran it in dartium, and saw the break point hit back in the editor.  This was very exciting and I'm finding myself bringing up TextMate less and less every week.

Thanks - Jim

[Daniel Rubel]

Glad you like the progress :-)

We are discussing exactly that topic... trying to figure out how to best represent referenced libraries, both dart: libraries and third party libraries, that are not imported into the user's workspace. This has implications for both browsing referenced code and discoverability.

[Phil Quitslund]

On Mon, Mar 12, 2012 at 7:22 AM, Jim Hugunin <jim...@google.com> wrote:

I am very happy to have the new files view.  Thanks!

We aim to please. :)

 

However, I noticed that I am now missing the ability to browse imported libraries that are somewhere else in my filesystem.  dart:core and dart:dom are the two most obvious cases.  I notice this most obviously when I use "Go to declaration" on something like String.  The editor very nicely brings up the appropriate file for me - but the file doesn't have any directory context and I feel a little bit at sea that I can't go looking for the other things in the same library.

As Dan said, this point is super-topical.  We're in the midst of hashing out a solution.

I'm not quite sure how I'd like to see this - but I recall that eclipse did a tolerable job of handling this for pure Java code?

Right.  The way eclipse handles this for Java is to provide a synthetic "referenced libraries" sub node under Java projects.  These libraries can then be expanded and explored.  Doing just this is one of the options on the table.

 

I really like the fact that every week the editor gets more pleasant to use.  Just last week I set a breakpoint in my dart code, ran it in dartium, and saw the break point hit back in the editor.  This was very exciting and I'm finding myself bringing up TextMate less and less every week.

Yay!