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).

                          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 …