Skip to main content

New Dart Editor Build 0.2.6.0_r15355


Dart Editor has a new build and it incorporates many of the changes that have been announced on these pages recently.  The change list includes modifications to the core library, as well as the html, SVG and io libraries. 

most SVG types no longer need the SVG prefix; SVGElement is now Element


Eric Clayberg fills us in on the details on the new Dart Editor build:
A new Dart Editor build is available at www.dartlang.org/editor. Changes include:
  • New Clean-Up to rename Element.elements to Element.children.
  • New Clean-Up to remove return type and name in function literal.
  • New "Convert Getter to Method" refactoring and Quick Assist action.
  • New Clean-Up to rename File.readAsText to File.readAsString.
  • New "Surround With..." Quick Assist.
  • UX changes and improvements in the Manage Launches dialog.
Breaking Change List:

      • dart:core changes
        • Exception constructor is no longer const, and usage is discouraged.
        • NullPointerException has been removed. Throwing null now throws NullThrownError. Accessing non-existing members on null throws NoSuchMethodError (Null just inherits noSuchMethod from Object).
      • dart:html changes
        • Element.elements has been deprecated in favor of Element.children.
      • dart:svg changes
        • Most SVG types will have their prefixes removed. So SVGFontElement will become FontElement. This does introduce some overlap with dart:html names, it’s recommend using "import 'dart:svg' as svg;" if you're mixing dart:html and SVG.
        • All dart:svg names will be 'Dartified' to have proper camel-casing. SVGFEDropShadowElement is now FEDropShadowElement.
        • SVGDocument, SVGElement and SVGSVGElement unfortunately will not immediately have their prefixes renamed as they require a much more significant refactoring to do so. They have been camel-cased though (to SvgElement, SvgSvgElement, etc).
      • dart:io changes
        • dart:io File.readAsText renamed to File.readAsString and File.readAsTextSync renamed to File.readAsStringSync.
                          And as always, view the changelog for the full list of changes, and to get started with the Editor see our tutorial.

                          As always, 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).

                          AngularDart is going all Dart

                          Until now, the multiple language flavors of Angular 2 were written as TypeScript source, and then automatically compiled to both JavaScript and Dart. We're happy to announce that we’re splitting the Angular 2 codebase into two flavors – a Dart version and a TypeScript/JavaScript version – and creating a dedicated AngularDart team.

                          This is amazing news for Dart developers because:

                          The framework will feel more like idiomatic Dart.It will make use of Dart features that couldn't work with the TypeScript flavor. It will be faster.
                          This is equally great news for our TypeScript and JavaScript developers, by the way. Cleaner API, performance gains, easier contributions. Read more on the Angular blog.

                          Angular 2 for Dart is used by many teams at Google. Most famously by the AdWords team, but many other Google teams build large, mobile-friendly web apps. Some of the top requests from these teams were: make the API feel like Dart, provide a faster edit-refresh cycle, and improve applicat…

                          The new AdWords UI uses Dart — we asked why

                          Google just announced a re-designed AdWords experience. In case you’re not familiar with AdWords: businesses use it to advertise on google.com and partner websites. Advertising makes up majority of Google’s revenue, so when Google decides to completely redo the customer-facing front end to it, it’s a big deal. The Dart team is proud to say that this new front end is built with Dart and Angular 2. Whenever you asked us whether Google is ‘even using Dart for anything,’ this is what we had in mind but couldn’t say aloud. Until now. We asked Joshy Joseph, the primary technical lead on the project, some questions. Joshy is focusing on things like infrastructure, application latency and development velocity, so he’s the right person to ask about Dart.Q: What exactly did we launch on Monday?It’s a complete redesign of the AdWords customer experience that is rolling out slowly as a test to a small initial set of advertisers. The most noticeable thing is probably the Material Design look and f…