Pass command line arguments onto platform apps which provide the right intent.

chrome/browser/extensions/platform_app_intent_dispatcher.h

+// Copyright (c) 2012 The Chromium Authors. All rights reserved.
+// Use of this source code is governed by a BSD-style license that can be
+// found in the LICENSE file.
+
+#ifndef CHROME_BROWSER_EXTENSIONS_PLATFORM_APP_INTENT_DISPATCHER_H_
+#define CHROME_BROWSER_EXTENSIONS_PLATFORM_APP_INTENT_DISPATCHER_H_
+#pragma once
+
+class ExtensionHost;
+
+namespace extensions {
+
+// Transforms and dispatches command line arguments to WebIntent data. A
+// window.intent object will be created in the |host| ExtensionHost's
+// render view if:
+//   - there is an argument on the command line, and
+//   - it has a MIME type for which the platform app associated with |host|
+//     provides the WebIntent action http://webintents.org/view.
+
+// The window.intent object will be setup as follows:
+//   - action will have http://webintents.org/view
+//   - type will have the MIME type for the file
+//   - data will have the filename as a file:/// URL.

[Greg Billock, 2012/03/28 14:21:02]

The current thinking is that if the contents are binary, they'll be set as a URL
(Blob), and if they are text, they'll come in as text. Do we need to account for
that here? That is, if your file type is text, the service is going to think the
content is "file://xxx".

[benwells, 2012/03/29 03:29:18]

Greg and I chatted about this and he filled me in on the work being done on the
payload data formats. As a result I'm going to hold off on this patch until
another change lands and then update to put the URL in the extras field.

+
+// |host| must not be NULL.
+void DispatchPlatformAppIntentData(ExtensionHost* host);
+
+}  // namespace extensions
+
+#endif  // CHROME_BROWSER_EXTENSIONS_PLATFORM_APP_INTENT_DISPATCHER_H_