Code generation for extensions api

chrome/common/extensions/api/tabs.json

Index: chrome/common/extensions/api/tabs.json
diff --git a/chrome/common/extensions/api/tabs.json b/chrome/common/extensions/api/tabs.json
index 004b4ce7d193c2841ef502daa76a47fb981a2750..55e2caf354049cb405565eefd136c50c8940767b 100644
--- a/chrome/common/extensions/api/tabs.json
+++ b/chrome/common/extensions/api/tabs.json
@@ -1,6 +1,7 @@
 [
   {
     "namespace": "tabs",
+    "generate": true,

[not at google - send to devlin, 2012/01/12 06:01:05]

it's a bit weird to do this now, since you're not using the generated code yet.

however; I can see that it's because you've copied it into the the test data,
and that it's nice to have it in sync.

however #2; it's going to get out of sync anyway, so I wonder if it's better to
just revert the changes to this and windows.json and change them back when
ready.

[calamity, 2012/01/12 22:59:20]

Reverted.

     "types": [
       {
         "id": "Tab",
@@ -61,6 +62,7 @@
       },
       {
         "name": "connect",
+        "nogenerate": true,

[not at google - send to devlin, 2012/01/12 06:01:05]

"nocompile"

         "type": "function",
         "description": "Connects to the content script(s) in the specified tab. The <a href='extension.html#event-onConnect'>chrome.extension.onConnect</a> event is fired in each content script running in the specified tab for the current extension. For more details, see <a href='content_scripts.html#messaging'>Content Script Messaging</a>.",
         "parameters": [
@@ -85,6 +87,7 @@
       },
       {
         "name": "sendRequest",
+        "nogenerate": true,
         "type": "function",
         "description": "Sends a single request to the content script(s) in the specified tab, with an optional callback to run when a response is sent back.  The <a href='extension.html#event-onRequest'>chrome.extension.onRequest</a> event is fired in each content script running in the specified tab for the current extension.",
         "parameters": [