Add a launchApp method to extension management API.
This makes it possible for new tab replacement extensions to recreate the same
app launch experience as the built-in NTP (pinned tabs, launch containers,
etc.)
Also add the extension version to data we report about extensions via
the management API.
BUG=56325,55474
TEST=An extension using chrome.experimental.management.launchApp(<id>) should
work to launch an app the same way that app gets launched from the built-in
new tab page.
Review URL: http://codereview.chromium.org/3381019
git-svn-id: svn://svn.chromium.org/chrome/trunk/src@60334 0039d316-1c4b-4281-b951-d872f2087c98
diff --git a/chrome/browser/extensions/extension_function_dispatcher.cc b/chrome/browser/extensions/extension_function_dispatcher.cc
index 6751671..c1867ca 100644
--- a/chrome/browser/extensions/extension_function_dispatcher.cc
+++ b/chrome/browser/extensions/extension_function_dispatcher.cc
@@ -273,13 +273,14 @@
// Management.
RegisterFunction<GetAllExtensionsFunction>();
+ RegisterFunction<LaunchAppFunction>();
RegisterFunction<SetEnabledFunction>();
- RegisterFunction<InstallFunction>();
RegisterFunction<UninstallFunction>();
// WebstorePrivate.
RegisterFunction<GetSyncLoginFunction>();
RegisterFunction<GetStoreLoginFunction>();
+ RegisterFunction<InstallFunction>();
RegisterFunction<SetStoreLoginFunction>();
}
