Initial commit of the Dart Chrome Extension APIs generators

tools/json_schema_compiler/dart/custom_hooks.dart

+/**
+ * This file contains custom hooks for the generated Chrome.* APIs.
+ *
+ * The format for a hook is:
+ *
+ *        // START (full type name) (property/method name)
+ *        (code)
+ *        // END
+ *
+ * For getters/setters, add 'get' or 'set' after the property name.
+ *
+ * The given code will be substituted instead of the generated one.
+ *
+ */
+

[not at google - send to devlin, 2013/01/25 18:14:33]

Whatever happens to these files - could we put each customisation in its own
file? I can see this file getting pretty enormous, and the // START // END thing
could get awkward.

However, as the JS customisation stuff works, it would be better to solve this
problem at the language/library level rather than at the compiler level.
Compiler complexity is worse than code complexity.

[sashab, 2013/01/29 08:27:13]

Done by fixing the way these files are passed in.

+
+// START app.window.AppWindow contentWindow
+// TODO(sashab, sra): Detect whether this is the current window, or an
+// external one, and return an appropriately-typed object
+WindowBase get contentWindow =>
+  JS("Window", "#.contentWindow", this._jsObject);
+// END
+
+// START app.runtime.LaunchData items get
+List<LaunchItem> get items() {
+  List<LaunchItem> items_final = new List<LaunchItem>();
+  for (var o in JS('List', '#.items', this._jsObject)) {
+    items_final.add(new LaunchItem._proxy(o));
+  }
+  return items_final;
+}
+// END
+