Added new fileBrowserPrivate and fileHandler extension APIs

chrome/common/extensions/api/extension_api.json

Index: chrome/common/extensions/api/extension_api.json
===================================================================
--- chrome/common/extensions/api/extension_api.json	(revision 81212)
+++ chrome/common/extensions/api/extension_api.json	(working copy)
@@ -4515,8 +4515,70 @@
     ]
   },
   {
+    "namespace":"fileSystem",

[asargent_no_longer_on_chrome, 2011/04/12 21:09:38]

would it make sense to call this namespace "fileBrowserActions" instead of
"fileSystem"? 

[Aaron Boodman, 2011/04/12 22:47:21]

If you parse the name "fileBrowserActions" as "(file browser) actions", it
actually makes a lot of sense. But most people with familiarity with the
extension system will parse it as "file (browser actions)" and be confused.

How about fileBrowserHandler to remove this ambiguity?

[zel, 2011/04/13 17:49:55]

I wanted to keep it generic enough in case we add more file browser related
stuff here in the future... we most certainly will. "fileBrowser" would do it
too - does that sound more acceptable to you?

[zel, 2011/04/13 17:49:55]

"fileBrowserHandler" it is.

+    "nodoc": "true",
+    "functions": [
+      {
+        "name": "resolveLocalFileSystemURL",
+        "description": "Allows the user to look up the Entry for a file or directory referred to by a local URL. ",
+        "parameters": [
+          {
+            "name": "url",
+            "type": "string",
+            "description": "A URL referring to a local file in a filesystem."
+          },
+          {
+            "name": "callback",
+            "type": "function",
+            "optional": "false",
+            "parameters": [
+              {
+                "name" : "entry",
+                "type": "object",
+                "optional": "true",
+                "description": "An Entry as a response to a file resolution request. It will have value of null if the request failed."
+              }
+            ]
+          }
+        ]
+      }
+    ],
+    "events": [
+      {
+        "name": "onExecuteAction",
+        "type": "function",
+        "description": "Fired when file system action is executed from ChromeOS file browser.",
+        "parameters": [
+          {
+            "name": "id",
+            "type": "string",
+            "description": "File browser action id as specified in the listener component's manifest."
+          },
+          {
+            "name": "fileUrls",

[Aaron Boodman, 2011/04/12 22:47:21]

How about "entryURLs", since they can be either files or directories.

[zel, 2011/04/13 17:49:55]

changed to 'entries' since this is what it is now and not url anymore

+            "type": "array",
+            "description": "Array of URLs of files that are targets of this action (selected in ChromeOS file browser).",
+            "items": { "type": "string" }
+          }
+        ]
+      }
+    ]
+  },
+  {
     "namespace":"fileBrowserPrivate",
     "nodoc": "true",
+    "types": [
+      {
+        "id": "FileBrowserTask",
+        "type": "object",
+        "description": "Represents information about available browser tasks. A task is an abstraction of an operation that the file browser can perform over a selected file set.",
+        "properties": {
+          "taskId": {"type": "string", "description": "The unique identifier of the task."},
+          "title": {"type": "string", "description": "Task title."},
+          "iconUrl": {"type": "string", "description": "Task icon url (from chrome://extension-icon/...)"}
+        }
+      }
+    ],
     "functions": [
       {
         "name": "requestLocalFileSystem",
@@ -4528,14 +4590,71 @@
             "optional": "false",
             "parameters": [
               {
+                "name" : "fileSystem",
                 "type": "object",
-                "isInstanceOf": "DOMFileSystem"
+                "optional": "true",
+                "description": "A DOMFileSystem instance for local file system access. null if the caller has no appropriate permissions."
               }
             ]
           }
         ]
       },
       {
+        "name": "getFileTasks",
+        "description": "Gets the of tasks that can be performed over selected files.",
+        "parameters": [
+          {
+            "name": "fileURLs",
+            "type": "array",
+            "description": "Array of selected file URLs",
+            "items": { "type": "string" }
+          },
+          {
+            "name": "callback",
+            "type": "function",
+            "optional": "false",
+            "parameters": [
+              {
+                "name": "tasks",
+                "type": "array",
+                "items": {"$ref": "FileBrowserTask"},
+                "description": "The list of available tasks that can be performed on all of the passed file paths."
+              }
+            ]
+          }
+        ]
+      },
+      {
+        "name": "executeTask",
+        "description": "Executes file browser task over selected files",
+        "parameters": [
+          {
+            "name": "taskId",
+            "type": "string",
+            "description": "The unique identifier of task to execute."
+          },
+          {
+            "name": "fileURLs",
+            "type": "array",
+            "description": "Array of file URLs",
+            "items": { "type": "string" }
+          },
+          {
+            "name": "callback",
+            "type": "function",
+            "optional": "false",
+            "parameters": [
+              {
+                "name": "success",
+                "type": "boolean",
+                "optional": "true",
+                "description": "True of task execution was successfully initiated."
+              }
+            ]
+          }
+        ]
+      },
+      {
         "name": "selectFiles",
         "type": "function",
         "description": "Select multiple files.",