Skip to main content

New Dart Editor Build With Expanded Exception Debugging and Autocompletion in Import Statements


Dart Editor has new build. Eric Clayberg fills us in on the details:
A new Dart Editor build is available at www.dartlang.org/editorChanges include:
  • Added a new launch configuration for Chrome packaged apps.
  • Add the ability to specify the break-on-exceptions behavior in the debugger (break on all exceptions, uncaught, or no breaking).
  • The editor now supports autocompletion in import statements!
  • Improved labeling on empty Dart search results
  • More navigation menu enhancements
  • Fix for resolving package: imports in dart scripts in HTML files
  • Various analysis and editor fixes
Breaking Change List:
  • Window.requestLayoutFrame is being renamed to window.setImmediate- it's functionally equivalent. The API is essentially a microtask API for executing callbacks after the current stack has unwound but before the next event and the rename is intended to be clearer about that. We've also improved the underlying behavior on IE (to use window.setImmediate) which will bring that more in-line with the WebKit behavior.
  • Element.getComputedStyle will no longer be asynchronous- it now returns the style rather than a Future. Be warned that this can invoke a browser layout operation- it's not a cheap API to use performance-wise.
  • Element.computedStyle is being removed. Use Element.getComputedStyle instead. Since this API had side-effects (invoking a browser re-layout), it was not appropriate as a getter.
  • Uri.fromString() renamed to Uri.parse()
Andas always,view the changelog for the full list of changes, and to get started with the Editor see our tutorial.
We invite you to join our Dart mailing list, ask questions on Stack Overflow, or file feature requests on dartbug.com.

Popular posts from this blog

Dart in 2016: The fastest growing programming language at Google, 2nd fastest growing in TIOBE Index

Dart was the fastest growing programming language at Google in 2016 with millions of lines of code written. It also made it to TIOBE Index Top 20 this month (see TIOBE's methodology).

It takes time to build something as ambitious as Dart and, in some ways, Dart is still in its infancy. But we're glad the hard work is starting to pay off.

Many thanks to our amazing community!

We're going to celebrate by ... releasing 1.22 next week (as per our usual 6 week release schedule).

A stronger Dart for everyone

We are constantly asking ourselves:
How do we make developers even more productive when writing Dart apps? We believe that a critical part of the answer to this question is to make strongmode – a sound static type system for Dart – the standard for all Dart developers.

Teams that use Dart to build apps like Soundtrap, AdWords, AdSense, and Greentea say they really enjoy using strong mode features, such as early error detection. In fact, teams that have switched completely to strong mode cite not only early error detection but also better code readability and maintainability as major benefits. We hear this both from small teams and – even more so – from large teams with hundreds of developers writing and maintaining millions of lines of Dart code. As Björn Sperber from Soundtrap says,
Strong mode and the smooth integration with IntelliJ is a joy to use and a huge improvement. If you’ve tried out Flutter, you’ve already used strong mode checks from the Dart analyzer.

Given the benefits …

AngularDart 2.1 and new Components

AngularDart got its own dedicated team 5 months ago. Last month, we launched 2.0 final on the Dart Developer Summit. Today, we’re releasing the first minor release after that: 2.1.

Since the focus of AngularDart is Productivity, Performance, Stability, there are no major breaking changes (see the changelog) — but a lot of behind-the-scenes improvements. Your apps will get slightly smaller and faster (even relative to 2.0 which already made huge strides in size and performance since the compiled-from-TypeScript days).

Many features that AngularJS had to implement for JavaScript and TypeScript are not needed in Dart (because Dart already has those features out-of-the-box). So we’re removing them from AngularDart. Renderer is deprecated in favor of plain-old dart:html. NgPlural is going away — Dart programs can use the package:intl library.

New components

On the Dart Developer Summit, we launched AngularDart Components — the material design widgets Google is using in customer-facing apps …