Skip to main content


Showing posts from July, 2013

Notes from the July 8 Dart language design meeting

The incomporable  Bob Nystrom  fills us in on the language design discussions taking place amongst Dart engineers. Here are his  notes from the July 8th language meeting : Here's my notes! JS interop and proxies Lars tried to make a little app using JS interop. He gets warnings from dart2js because JS interop returns a proxy. The only way to get rid of the warnings is to edit the interop package itself to make it return the dynamic type. Gilad says we don't currently have a solution for general purpose proxies, though we've discussed a couple. The biggest problem is checked mode. If it was just static warnings, we could do an annotation or something to turn off the warning. For general purpose proxies, "implements dynamic" may be the best thing: it is a black hole that implements anything. We will have to educate people: most of the time you want to implement some specific type and not turn them all off like this. One thing

Introducing polymer.dart

Dart engineer John Messerly announces the launch of polymer.dart, a port of the  Polymer stack . The Web UI package will be maintained for some time, but will eventually be replaced by polymer.dart. Here is John's  original post introducing polymer.dart : Hello Dartisans, Since we started Web UI, we've had a goal to bring the latest web standards like Web Components and Model-Driven Views to Dart developers. There have been some great developments since we started: Web Components has progressed into a set of detailed specs ( Custom Elements , Shadow DOM , HTML Templates , HTML Imports ) with interest and implementation by multiple browser vendors. Model-Driven Views has new APIs ( Node.bind , TemplateElement.model ) that allow custom elements to participate in the binding system, as well as the ability to plug in custom syntax, such as the fancy_syntax package. dart:mirrors is now implemented in dart2js! Last but not least: the development of the Poly