Skip to main content

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 Polymer project. Polymer is a new type of JavaScript library for the web that builds on top of these emerging standards.

Today we continue our mission by publishing the beginnings of polymer.dart, our port of the Polymer stack. We’re pushing several packages to Pub: observe, mdv, shadow_dom, and the polymer.dart package.  The Dart team is collaborating with the Polymer team to ensure that polymer.dart elements and polyfills are fully compatible with Polymer.

This is only the beginning. Polymer and web components are evolving, and we’re going to keep bringing that to you. Some of the things we’ll be working on are:
  • declarative <polymer-element> and custom elements.
  • more new, up-to-date polyfill packages, like html_imports.
  • removing the mandatory compiler step for polymer.dart. Just edit, save & refresh!
  • bring the Polymer UI elements to Dart.
  • up to date documentation for all of this shiny new stuff.

It's still very early for polymer.dart, but we welcome you to try out the new packages. We’ll be maintaining the web_ui package for a considerable time, but will eventually be sunsetting it in favor of Polymer. Thanks in advance for your feedback as we continue the port and evolve the specs and implementations. We hope you’re as excited as we are about Polymer, and can't wait to see what you build!

Thanks!

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…