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

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 …