Dart News & Updates

Dart Editor has a new build that supports theming, better error reporting,  disabled support for the old getter definition syntax, numerous changes to the dart:html library and more. Devon Carew fills us in on the details  on this new build : A new Dart Editor build is available at  www.dartlang.org/editor . Changes include: Added support for theming the Editor - check out the 'Visual Themes' page in the preferences dialog. The extract local Variable refactoring can now extract part of a string literal. Several build.dart improvements, including better error reporting. There's now an option to not warn when a class with noSuchMethod() has unimplemented members. Added an analyzer command line option: --type-checks-for-inferred- types. This lets command line users get the same warnings they would get with the editor. Analysis changes to support the upcoming iterator changes. Html editor tweaks and improvements. Breaking changes: ...

Watch another great episode of Dartisans dealing with using  Web Components   with  Dart .  This  episode features presentations by Dimitri Glazkov (one of the creators of Web Components) and John Messerly and Siggi Cherem (who helped build the dart-lang/dart-web-components library).   You can follow along with the open-source  dart-web-components work on Github . As always, we invite you to join our  Dart mailing list , ask questions on  Stack Overflow , or file feature requests on  dartbug.com .

SDK packages are now available on pub.dartlang.org. This means that you can now declare a dependency in the following manner:  Before this change, you had to rely on the sdk: Dan Grove provides the details :  I've just finished uploading the packages from the dart repo's pkg directory to pub - this means that you can use  args http intl logging meta oauth2 unittest webdriver through regular pub dependencies in your pubspec.yaml, rather than sdk: dependencies. We'll keep these updated when we do our weekly releases from trunk. Enjoy! As always, we invite you to join our  Dart mailing list , ask questions on  Stack Overflow , or file feature requests on  dartbug.com .

Don't know how to get started with testing your Dart code? This  new article  by Shailen Tuli provides a gentle introduction to creating a Dart package and writing unit tests for it.  Read this article to get started and then find out more about  Pub packages  and  Unit Testing with Dart . As always, we invite you to join our  Dart mailing list , ask questions on  Stack Overflow , or file feature requests on  dartbug.com .

In a new article  Kathy Walrath describes the conventions for writing comments in Dart code. Please read to know about the document comment style used by the Dart team and to suggest changes and improvements. As always, we invite you to join our  Dart mailing list , ask questions on  Stack Overflow , or file feature requests on  dartbug.com .

Introspection and reflection are important parts of Dart. In this article on the subject, Gilad Bracha  tells us about reflection using Mirrors . The topics covered in this article represent the bleeding edge in Dart: while not everything if fully implemented, the article lays out Dart's vision for these subjects and explains the reasoning behind some of the design decisions.  Lots of mirrors! As always, we invite you to join our  Dart mailing list , ask questions on  Stack Overflow , or file feature requests on  dartbug.com . (Image courtesy of  http://www.flickr.com/photos/jrgmontero/4794190593/ )

Dart engineer  Bob Nystrom  has  posted the notes  from the November 26th language design meeting. He writes: Kasper and Lars were out, so this was a short one: Mixins Gilad says mixins will not be in M2. He's going to put out an updated proposal this week with spec language and everything in it. Hopefully it won't cause too much indigestion. What's left for M2? Gilad says mostly minor a bugs. A few doc comment ones. Config-specific code Gilad has some ideas but he's not quite ready to discuss them yet. He's been thinking about the issue for 20 years. :) Parameter type validation I brought up that the corelib is now starting to manually validate parameter types in the body of methods using  is  in . For example: num max(num a, num b) {   if (a is! num) throw new ArgumentError(a);   if (b is! num) throw new ArgumentError(b);   ... } How do we feel about tha...