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

chrome/browser/extensions/api/app/app_api.cc

Index: chrome/browser/extensions/api/app/app_api.cc
diff --git a/chrome/browser/extensions/api/app/app_api.cc b/chrome/browser/extensions/api/app/app_api.cc
index d429710f0fb7355c0a083c9e8da9509cbc7178bc..ae230a2ce018f79bf5ffb8f15dd4a5e0864ea745 100644
--- a/chrome/browser/extensions/api/app/app_api.cc
+++ b/chrome/browser/extensions/api/app/app_api.cc
@@ -4,8 +4,10 @@
 
 #include "chrome/browser/extensions/api/app/app_api.h"
 
+#include "base/json/json_writer.h"
 #include "base/values.h"
 #include "base/time.h"
+#include "base/utf_string_conversions.h"
 #include "chrome/browser/extensions/app_notification_manager.h"
 #include "chrome/browser/extensions/extension_event_router.h"
 #include "chrome/browser/extensions/extension_service.h"
@@ -120,4 +122,24 @@ void AppEventRouter::DispatchOnLaunchedEvent(
       extension->id(), kOnLaunchedEvent, "[]", NULL, GURL());
 }
 
+// static.
+void AppEventRouter::DispatchOnLaunchedEventWithUrl(
+    Profile* profile, const Extension* extension, const string16& action,
+    const std::string& mime_type, const GURL& url) {
+  ListValue args;
+  DictionaryValue* launch_data = new DictionaryValue();
+  DictionaryValue* intent = new DictionaryValue();
+  intent->SetString("action", UTF16ToUTF8(action));
+  intent->SetString("type", mime_type);
+  DictionaryValue* extra_data = new DictionaryValue();
+  extra_data->SetString("url", url.spec());
+  intent->Set("extra_data", extra_data);
+  launch_data->Set("intent", intent);
+  args.Append(launch_data);
+  std::string json_args;
+  base::JSONWriter::Write(&args, &json_args);
+  profile->GetExtensionEventRouter()->DispatchEventToExtension(
+      extension->id(), kOnLaunchedEvent, json_args, NULL, GURL());

[Mihai Parparita -not on Chrome, 2012/05/15 00:39:28]

Seems like you would also need to update experimental.app.json to include the
launch data parameter (and define the type, for validation).

Additionally, if you include the type in the JSON file, the JSON schema compiler
will generate a struct for you that has a ToValue() method, so that you don't
need to hardcode the key names.

For an example, see the alarms API: 

The Alarm type is defined here:
http://code.google.com/searchframe#OAMlx_jo-ck/src/chrome/common/extensions/a...

The  generated code looks like:
http://code.google.com/searchframe#OAMlx_jo-ck/src/out/Release/obj/gen/chrome...

And is used here:
http://code.google.com/searchframe#OAMlx_jo-ck/src/chrome/browser/extensions/...

[Greg Billock, 2012/05/15 00:54:59]

If we're using an idl value, we could put "action", "type", "data", and "extras"
in it, as for the Alarm type, right? We couldn't pass any serializable JS
objects, but it'd give quite a bit of flexibility for passing text. Or is this
facility something different?

On 2012/05/15 00:39:28, Mihai Parparita wrote:

[benwells, 2012/05/16 01:35:29]

My understanding is that the IDL or JSON provides some nice autogenerated code
for you, which makes creating these kind of parameters easier. It doesn't change
what can go in them.

I am working on adding a FileEntry as a data parameter to the intent, which will
happen in js with some extension hookery.

[benwells, 2012/05/18 03:36:02]

I've added the launchData field into the json, but I'm not using the handy
structure - the data format here is different to what gets delivered to the app,
being transformed in a custom event dispatcher.

+}
+
 }  // namespace extensions