DART :: firstElementChild y lastElementChild

En las nuevas versiones de DART algunos de los métodos nativos de DOM se han ido marcando como obsoletos dejándolos disponibles por si los necesitamos de manera absolutamente necesaria y no existe por el momento otra opción.

Algunos ejemplos de estos métodos son lastElementChild y firstElementChild.

Dentro de la interfaz Element podemos verlos definidos de este modo.

Continue reading “DART :: firstElementChild y lastElementChild”

BREAKING CHANGE: Timer interface moved to dart:isolate

New breaking change for DART.


With revision


the Timer interface moved to the “dart:isolate” library. This will
allow different environments (e.g. Dartium) to provide their own Timer
implementations making it easier to write portable code which relies
on an event loop and delayed execution.

Currently the only environment which has a working Timer
implementation is the standalone Dart VM binary. If you have been
using the Timer interface before, you will now need to import the
“dart:isolate” library instead of the “dart:io” library.

Continue reading “BREAKING CHANGE: Timer interface moved to dart:isolate”

New DART Teams’ Weekly digest

I leave new DART Team’s Weekly digest.


In the Dart to JavaScript Compiler we improved generated code for simple bailout functions, enabled speculative optimizations in methods called from loops and added support for discovering when fields are effectively final, but not marked as such. We also removed unnecessary braces from generated code, fixed a few browser compatibility issues (http://dartbug.com/3152and others) and fixed some issues with isolates.

Continue reading “New DART Teams’ Weekly digest”

New Dart Editor build 8350

A new Dart Editor build is available:


Highlights for build 8350:
The command-line debugger is now enabled. Debug your server apps! Debug dart2js!
Fixed 15+ static analysis issues.
Bigger stepping granularity in debugging; one step now equals one source line.
When re-launching your app we re-cycle the Dartium instance when possible, instead of always killing the process and restarting Dartium.
Various Searchbox fixes.
Dart2js is now the default (and only) Dart-to-Javascript compiler in the editor.
View the full change log:

Continue reading “New Dart Editor build 8350”

Dart Team’s digest

Hi, I attached new Dart Team’s digest.

Very very interesting and important if you’re using dart:dom.

It’s been a while since the last update, but here’s a summary of some of the recent events in Dart-land.

In the Dart to JavaScript Compiler we’re getting ready to deprecate frog and remove it from the SDK. We increased test coverage for dart2js on build bots, fixed a bunch of browser compatibility issues and landed liveness analysis resulting in 3-4% code size reduction and less temporary variables. Finally, we’re now generating smaller code for simple tear-off closures.

In Dartium, we’re phasing out dart:dom and are now supporting wrapperless dart:html.

For the Dart Editor we now have new and improved Editor documentation! We also improved code completion in the absence of explicit type information. We have improved type inference in if, while, for and for-in statements and all launches now run in checked mode by default. All launches (JavaScript and Dartium) now serve from a server and not from a file: url. (This plays better with loading resources using XHR and the browser security model). Analysis results now cached between sessions which leads to faster start-up. Finally, we fixed a number of issues including, an issue with lots of warnings related to final fields and a performance issue with the outline view.

For Dart Server side libraries we published instructions on building native C/C++ extensions for the standalone Dart VM, landed feature enhancements and bug fixing in the HTTP, File and Directory interfaces. Finally, we’ve introduced hardening of the APIs to deal gracefully with unexpected arguments.

Anders Sandholm

Post wrote by Moisés Belchín

Important change on compilation DART to JavaScript process

Recently DART Team published a note on the DART discuss where they tell us has been an important and significant change on the DART to Javascript compilation process.

Currently, the way to run our applications written in DART is compile it to JavaScript so that browsers can run our code.

All of this will change when the virtual machine that runs our DART code natively is deployed and supported by most popular browsers, in particular Google Chrome will support it natively.

Continue reading “Important change on compilation DART to JavaScript process”

String + eliminado de dart2js y proximamente de VM

Hoy he leído un post en la lista oficial de DART donde mencionaban que el nuevo compilador de Dart a Javascript [dart2js] ha eliminado el soporte del operador “+” en la concatenación de cadenas.

También comentan que en breve la máquina virtual va a dejar de mantener el operador + en la concatenación de strings. Como indica Seth Ladd es buen momento para revisar nuestros códigos.

Continue reading “String + eliminado de dart2js y proximamente de VM”

Create a website or blog at WordPress.com

Up ↑