Native entry point for spawnDomUri

tools/dom/templates/html/dartium/html_dartium.darttemplate

Index: tools/dom/templates/html/dartium/html_dartium.darttemplate
diff --git a/tools/dom/templates/html/dartium/html_dartium.darttemplate b/tools/dom/templates/html/dartium/html_dartium.darttemplate
index 2c92c8c241d913a8fcafb35b9fb82457763608c9..7696929782a99e186e028dbec12d92fcd439fb6c 100644
--- a/tools/dom/templates/html/dartium/html_dartium.darttemplate
+++ b/tools/dom/templates/html/dartium/html_dartium.darttemplate
@@ -118,3 +118,15 @@ HtmlDocument get document {
   _document = window.document;
   return _document;
 }
+
+/**
+ * Spawn a DOM isolate using the given URI in the same window.
+ * This isolate is not concurrent.  It runs on the browser thread
+ * with full access to the DOM.
+ * Note: this API is still evolving and may move to dart:isolate.
+ */
+@Experimental()
+Future<Isolate> spawnDomUri(Uri uri, List<String> args, message) {

[Siggi Cherem (dart-lang), 2014/03/24 16:51:56]

should we add this API also to the html/common or html/dart2js templates? (with
an unimplemented exception or forwarding it to the dart:isolates API)

I'm particular, I'm not sure if the analyzer will complain about using a
non-existing API if we only have it in this template and not the others.

[vsm, 2014/03/24 21:52:57]

Good point.  I'll do that in a follow-up CL.

On 2014/03/24 16:51:56, Siggi Cherem (dart-lang) wrote:

+  // TODO(vsm): Plumb arguments and return value through.
+  return _Utils.spawnDomUri(uri.toString());
+}