Adds @HtmlImport with both dynamic and transformer based implementations. Still need an HtmlInliner…

CHANGELOG.md

Index: CHANGELOG.md
diff --git a/CHANGELOG.md b/CHANGELOG.md
index 6aeadaed0d02ad16ebac7bd077645793485b07d7..142174006cf0172e266589056905d8a98d5a5f5d 100644
--- a/CHANGELOG.md
+++ b/CHANGELOG.md
@@ -1,3 +1,27 @@
+#### 0.10.2-dev
+  * Added the `HtmlImport` annotation. This can be added to any library
+    declaration and it will inject an html import to the specified path into the
+    head of the current document, which allows dart files to declare their html
+    dependencies. Paths can be relative to the current dart file or they can be
+    in `package:` form.
+
+    *Note*: Html imports included this way cannot contain dart script tags. The
+    mirror based implementation injects the imports dynamically and dart script
+    tags are not allowed to be injected in that way.
+
+    There is also a transformer supplied which will inline these imports into
+    the head of your document at compile time, it can be used like this:
+
+      transformers:
+      # Must include the `initialize` transformer first.
+      - initialize:
+          entry_point: web/index.dart
+          html_entry_point: web/index.html
+      - web_components/build/html_import_annotation_inliner:

[Siggi Cherem (dart-lang), 2015/02/12 16:49:44]

maybe we should provide a second transformer:
 - html_initialize

that combines what initialize + html_import_annotation_inliner do.

If a user depends on initialize on their own, they can use this form you present
here, but if they don't, they can do everything with a single transformer.

WDYT?

[jakemac, 2015/02/12 17:04:09]

In the new version of this stuff there will only be a web_components
transformer, which itself calls the initialize transformer (with an html imports
plugin).

+          # The bootstrap file created by the `initialize` transformer.
+          bootstrap_file: test/index.bootstrap.dart
+          html_entry_point: test/index.html
+
 #### 0.10.1
   * Added the `CustomElementProxy` annotation. This can be added to any class
     which proxies a javascript custom element and is the equivalent of calling