New Dart Editor build 0.2.10.1_r16761

[Eric Clayberg]

A new Dart Editor build is available at www.dartlang.org/editor. Changes include:

• Windows love!
  
• You can now debug command-line applications from the editor! This was a long-awaited feature.
• The command-line dart_analyzer tool is now available in the Windows SDK (dart-sdk/bin/dart_analyzer.bat).
• Various Windows bug fixes and UX cleanup.
• Several changes in support of building Chrome Apps:
  
• Add a setting to allow the user to pass custom flags to dart2js (like --disallow-unsafe-eval). To configure this, right-click on a project and choose 'Properties'.
• Added a manifest.json editor.
• Improved support for Dart code in html files
  
• Syntax highlighting
• Analysis for inline scripts.
• Package version information is now shown in the Files View
  
• The Problems view can now optionally just show problems for the currently selected project.
  
• Improved css and yaml editors
  
• Filter log entries during test execution
  
• Various analysis, editor, theming and refactoring fixes
  

And as always,view the changelog for the full list of changes, and to get started with the Editor see our tutorial.

--

Eric Clayberg

Dart Editor Team

Google, Inc.

[John Evans]

Wow you guys really responded fast on that Chrome App stuff.  Great job!

[George Moschovitis]

Thanks!

Some annoying errors went away, and the improved editors for html/css are very helpful.

Any luck we can see integrated support for Git in a future version?

-g.

[Seth Ladd]

Hi George,

Any luck we can see integrated support for Git in a future version?

I don't see it on the radar. Dart Editor is trying to stay light weight, and SCM seems to tip the scales. There is an Eclipse Plugin and a plugin for IntelliJ if you want more full-featured editors that have support for SCMs like git.

Thanks for your question!

Seth

[George Moschovitis]

I don't see it on the radar. Dart Editor is trying to stay light weight, and SCM seems to tip the scales. There is an Eclipse Plugin 

It's a pity :(

Is the Eclipse plugin actively maintained? Is it synchronized with the Dart Editor releases?

-g. 

[Ivo Balbaert]

Hi Dart team,

 

I downloaded this version today but now A Dart console program when launched (as is default) with debugging enabled stalls and doesn't produce any output, whether or not the script contains a breakpoint.

 

Simple test example:

main() {

var a = 5;

a +=

2;

print(

'$a');

}

Even only a print('test'); does not execute.

I made a fresh install of the Dart environment with the same result.

I run Windows 7.

Did I overlook something or what could be wrong here ?

 

Cheers,

Ivo

 

Op dinsdag 8 januari 2013 18:43:32 UTC+1 schreef Eric Clayberg (Google) het volgende:

[Brian Wilkerson]

George,

Is the Eclipse plugin actively maintained? Is it synchronized with the Dart Editor releases?

Yes and yes. They are developed and maintained by the same team and share most of the same code. We are happy to get feature requests for either product if you find something lacking (you can submit either at http://code.google.com/p/dart/issues).

Brian

[Devon Carew]

I downloaded this version today but now A Dart console program when launched (as is default) with debugging enabled stalls and doesn't produce any output, whether or not the script contains a breakpoint.

Hi Ivo, I'm not able to reproduce the behavior you describe. Is this only with debugging enabled? Are there any exceptions in the log (viewable from the 'feedback' button)?

Devon

--
Consider asking HOWTO questions at Stack Overflow: http://stackoverflow.com/tags/dart
 
 

--
Devon Carew

Software Engineer

Google, Inc.

[Ivo Balbaert]

Hi Devon,

 

I now found that when I only had this simple progam open in Dart Editor debugging works!

So either it could have something to do with the other applications open in the editor (which is strange because this should not interfere), or it could be that the debugging needs a lot more memory.

When I closed everything except the test-application, I had 308 Mb free memory, when the problem occurred as you see beneath I had only 101 Mb left.

Perhaps on Windows the environment needs more memory allocation to enable debugging ?

 

Thanks for looking into this,

Ivo

 

P.S:

 

The Feedback buttongave this info:

 

Editor: 0.2.10_r16761 (2013-01-07)
OS: Windows 7 - amd64 (6.1)
JVM: 1.6.0_27
# projects: 31
# open dart files: 1
auto-run pub: false
mem max/total/free: 889 / 190 / 101 MB
thread count: 29
analysis: 0 tasks, 106 libraries, 6 contexts
index: 145091 relationships and 0 attributes in 25708 elements in 681 resources stored in 4 MB on disk

SDK installed: true
Dartium installed: true

When I had the problem, every console program which ran fine in the previous version hanged when debugging is enabled as is the default.

As soon as debugging is unchecked, the program continues and produces results.

 

To be complete I include the .log file in C:\Users\ivo\DartEditor\.metadata:

 

!SESSION 2013-01-14 09:47:36.306 -----------------------------------------------
eclipse.buildId=unknown
java.version=1.6.0_27
java.vendor=Sun Microsystems Inc.
BootLoader constants: OS=win32, ARCH=x86_64, WS=win32, NL=nl_BE
Command-line arguments:  -os win32 -ws win32 -arch x86_64 -data @user.home\DartEditor

!ENTRY com.google.dart.tools.core 4 0 2013-01-14 09:47:57.629
!MESSAGE while scanning a simple key; could not found expected ':'
!STACK 0
while scanning a simple key
 in "<string>", line 19, column 3:
      some_opensource_library
      ^
could not found expected ':'
 in "<string>", line 20, column 8:
        git:
           ^

 at org.yaml.snakeyaml.scanner.ScannerImpl.stalePossibleSimpleKeys(ScannerImpl.java:458)
 at org.yaml.snakeyaml.scanner.ScannerImpl.needMoreTokens(ScannerImpl.java:278)
 at org.yaml.snakeyaml.scanner.ScannerImpl.checkToken(ScannerImpl.java:223)
 at org.yaml.snakeyaml.parser.ParserImpl$ParseBlockMappingKey.produce(ParserImpl.java:562)
 at org.yaml.snakeyaml.parser.ParserImpl.peekEvent(ParserImpl.java:160)
 at org.yaml.snakeyaml.parser.ParserImpl.checkEvent(ParserImpl.java:145)
 at org.yaml.snakeyaml.composer.Composer.composeMappingNode(Composer.java:230)
 at org.yaml.snakeyaml.composer.Composer.composeNode(Composer.java:159)
 at org.yaml.snakeyaml.composer.Composer.composeMappingNode(Composer.java:237)
 at org.yaml.snakeyaml.composer.Composer.composeNode(Composer.java:159)
 at org.yaml.snakeyaml.composer.Composer.composeMappingNode(Composer.java:237)
 at org.yaml.snakeyaml.composer.Composer.composeNode(Composer.java:159)
 at org.yaml.snakeyaml.composer.Composer.composeDocument(Composer.java:122)
 at org.yaml.snakeyaml.composer.Composer.getSingleNode(Composer.java:105)
 at org.yaml.snakeyaml.constructor.BaseConstructor.getSingleData(BaseConstructor.java:120)
 at org.yaml.snakeyaml.Yaml.loadFromReader(Yaml.java:480)
 at org.yaml.snakeyaml.Yaml.load(Yaml.java:399)
 at com.google.dart.tools.core.utilities.yaml.PubYamlUtils.parsePubspecYamlToMap(PubYamlUtils.java:163)
 at com.google.dart.tools.core.internal.model.DartProjectImpl.recomputePackageInfo(DartProjectImpl.java:609)
 at com.google.dart.tools.core.internal.model.DartProjectImpl.buildStructure(DartProjectImpl.java:798)
 at com.google.dart.tools.core.internal.model.OpenableElementImpl.generateInfos(OpenableElementImpl.java:480)
 at com.google.dart.tools.core.internal.model.DartElementImpl.openWhenClosed(DartElementImpl.java:563)
 at com.google.dart.tools.core.internal.model.DartElementImpl.getElementInfo(DartElementImpl.java:331)
 at com.google.dart.tools.core.internal.model.DartElementImpl.getElementInfo(DartElementImpl.java:316)
 at com.google.dart.tools.core.internal.model.DartElementImpl.getChildren(DartElementImpl.java:267)
 at com.google.dart.tools.core.internal.model.DartElementImpl.getChildrenOfType(DartElementImpl.java:281)
 at com.google.dart.tools.core.internal.model.DartProjectImpl.getDartLibraries(DartProjectImpl.java:290)
 at com.google.dart.tools.core.internal.model.DartModelImpl.getDartLibraries(DartModelImpl.java:136)
 at com.google.dart.tools.core.internal.model.HTMLFileImpl.buildStructure(HTMLFileImpl.java:99)
 at com.google.dart.tools.core.internal.model.OpenableElementImpl.generateInfos(OpenableElementImpl.java:480)
 at com.google.dart.tools.core.internal.model.DartElementImpl.openWhenClosed(DartElementImpl.java:563)
 at com.google.dart.tools.core.internal.model.DartElementImpl.getElementInfo(DartElementImpl.java:331)
 at com.google.dart.tools.core.internal.model.DartElementImpl.getElementInfo(DartElementImpl.java:316)
 at com.google.dart.tools.core.internal.model.HTMLFileImpl.getReferencedLibraries(HTMLFileImpl.java:72)
 at com.google.dart.tools.debug.ui.internal.util.LaunchUtils.getDartLibraries(LaunchUtils.java:239)
 at com.google.dart.tools.debug.ui.internal.util.LaunchUtils.isLaunchableWith(LaunchUtils.java:426)
 at com.google.dart.tools.debug.ui.internal.dartium.DartiumLaunchShortcut.testSimilar(DartiumLaunchShortcut.java:142)
 at com.google.dart.tools.debug.ui.internal.util.AbstractLaunchShortcut.getAssociatedLaunchConfigurations(AbstractLaunchShortcut.java:73)
 at com.google.dart.tools.debug.ui.internal.util.LaunchUtils.getExistingLaunchesFor(LaunchUtils.java:263)
 at com.google.dart.tools.debug.ui.internal.util.LaunchUtils.getLaunchFor(LaunchUtils.java:313)
 at com.google.dart.tools.debug.ui.internal.dialogs.ManageLaunchesDialog.selectLaunchConfigFromPage(ManageLaunchesDialog.java:565)
 at com.google.dart.tools.debug.ui.internal.dialogs.ManageLaunchesDialog.createDialogUI(ManageLaunchesDialog.java:495)
 at com.google.dart.tools.debug.ui.internal.dialogs.ManageLaunchesDialog.createDialogArea(ManageLaunchesDialog.java:326)
 at org.eclipse.jface.dialogs.TitleAreaDialog.createContents(TitleAreaDialog.java:155)
 at org.eclipse.jface.window.Window.create(Window.java:431)
 at org.eclipse.jface.dialogs.Dialog.create(Dialog.java:1089)
 at org.eclipse.jface.window.Window.open(Window.java:790)
 at com.google.dart.tools.debug.ui.launch.ManageLaunchesAction.run(ManageLaunchesAction.java:42)
 at com.google.dart.tools.debug.ui.launch.ManageLaunchesHandler.execute(ManageLaunchesHandler.java:37)
 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)
 at org.eclipse.ui.internal.handlers.HandlerService.executeCommand(HandlerService.java:169)
 at org.eclipse.ui.internal.handlers.SlaveHandlerService.executeCommand(SlaveHandlerService.java:241)
 at org.eclipse.ui.menus.CommandContributionItem.handleWidgetSelection(CommandContributionItem.java:829)
 at org.eclipse.ui.menus.CommandContributionItem.access$19(CommandContributionItem.java:815)
 at org.eclipse.ui.menus.CommandContributionItem$5.handleEvent(CommandContributionItem.java:805)
 at org.eclipse.swt.widgets.EventTable.sendEvent(EventTable.java:84)
 at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1053)
 at org.eclipse.swt.widgets.Display.runDeferredEvents(Display.java:4165)
 at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:3754)
 at org.eclipse.ui.internal.Workbench.runEventLoop(Workbench.java:2696)
 at org.eclipse.ui.internal.Workbench.runUI(Workbench.java:2660)
 at org.eclipse.ui.internal.Workbench.access$4(Workbench.java:2494)
 at org.eclipse.ui.internal.Workbench$7.run(Workbench.java:674)
 at org.eclipse.core.databinding.observable.Realm.runWithDefault(Realm.java:332)
 at org.eclipse.ui.internal.Workbench.createAndRunWorkbench(Workbench.java:667)
 at org.eclipse.ui.PlatformUI.createAndRunWorkbench(PlatformUI.java:149)
 at com.google.dart.tools.deploy.DartIDEApplication.start(DartIDEApplication.java:113)
 at org.eclipse.equinox.internal.app.EclipseAppHandle.run(EclipseAppHandle.java:196)
 at org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher.runApplication(EclipseAppLauncher.java:110)
 at org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher.start(EclipseAppLauncher.java:79)
 at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:344)
 at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:179)
 at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
 at sun.reflect.NativeMethodAccessorImpl.invoke(Unknown Source)
 at sun.reflect.DelegatingMethodAccessorImpl.invoke(Unknown Source)
 at java.lang.reflect.Method.invoke(Unknown Source)
 at org.eclipse.equinox.launcher.Main.invokeFramework(Main.java:622)
 at org.eclipse.equinox.launcher.Main.basicRun(Main.java:577)
 at org.eclipse.equinox.launcher.Main.run(Main.java:1410)
 at org.eclipse.equinox.launcher.Main.main(Main.java:1386)

Op zondag 13 januari 2013 14:44:15 UTC+1 schreef Devon Carew het volgende:

[Bob Nystrom]

On Mon, Jan 14, 2013 at 1:08 AM, Ivo Balbaert <ivo.ba...@gmail.com> wrote:

!STACK 0
while scanning a simple key
 in "<string>", line 19, column 3:
      some_opensource_library
      ^
could not found expected ':'
 in "<string>", line 20, column 8:
        git:
           ^

 at org.yaml.snakeyaml.scanner.ScannerImpl.stalePossibleSimpleKeys(ScannerImpl.java:458)

This looks like you might have an error in your pubspec. Can you show us the contents of your pubspec.yaml file?

Thanks!

- bob

[Devon Carew]

Ditto what Bob said. It looks like one of the other open applications had a pubspec.yaml file that we didn't like, and the resulting exception caused the launch to fail. I think we need our pubspec parsing and our launch framework to be a bit more robust in the face of errors.

Devon

--
Consider asking HOWTO questions at Stack Overflow: http://stackoverflow.com/tags/dart
 
 

[Daniel Rubel]

And we've been moving in that direction...

https://codereview.chromium.org/11884046/