Add registerPort / lookupPort to generated interfaces with documentation

lib/dom/templates/html/interface/interface_Window.darttemplate

Index: lib/dom/templates/html/interface/interface_Window.darttemplate
diff --git a/lib/dom/templates/html/interface/interface_Window.darttemplate b/lib/dom/templates/html/interface/interface_Window.darttemplate
index cc575b1c3c1f450f7b5d2d11bb65db13e60f8c3d..2cce70016a5bd7871585fbe8022f493ece59a2a1 100644
--- a/lib/dom/templates/html/interface/interface_Window.darttemplate
+++ b/lib/dom/templates/html/interface/interface_Window.darttemplate
@@ -8,6 +8,19 @@ $!COMMENT
 interface $ID$EXTENDS {
 
   /**
+   * Register a [port] on this window under the given [name].  This
+   * port may be retrieved by any isolate (or JavaScript script)
+   * running in this window.
+   */
+  void registerPort(String name, SendPortSync port);

[Siggi Cherem (dart-lang), 2012/07/10 23:50:41]

should this be registerSyncPort? (do we expect to later have a registerAsyncPort
as well?)

[vsm, 2012/07/10 23:53:24]

We do want to allow SendPort (i.e., the async one) at some point.  Not sure
whether to just have one register function (with a var or to be determined
common base type param) or to break it in two.

On 2012/07/10 23:50:41, sigmund wrote:

+
+  /**
+   * Lookup a port by its [name].  Return null if no port is
+   * registered under [name].
+   */
+  SendPortSync lookupPort(String name);
+
+  /**
    * Executes a [callback] after the next batch of browser layout measurements
    * has completed or would have completed if any browser layout measurements
    * had been scheduled.