Allow chromedriver to install an extension and get all installed extension IDs.

chrome/browser/automation/automation_provider_observers.h

Index: chrome/browser/automation/automation_provider_observers.h
diff --git a/chrome/browser/automation/automation_provider_observers.h b/chrome/browser/automation/automation_provider_observers.h
index 48b2cc41adf4d93188344363eccd0ce38a40188c..0fb745be1e25d0eb587e6274dd58b944536e5969 100644
--- a/chrome/browser/automation/automation_provider_observers.h
+++ b/chrome/browser/automation/automation_provider_observers.h
@@ -336,11 +336,17 @@ class ExtensionUninstallObserver : public content::NotificationObserver {
 class ExtensionReadyNotificationObserver
     : public content::NotificationObserver {
  public:
+  // Creates an observer that replies using the old IPC automation method.
   ExtensionReadyNotificationObserver(ExtensionProcessManager* manager,

[dennis_jeffrey, 2011/11/22 23:32:16]

Do we still need this old version of the function? Can we get rid of it?

[kkania, 2011/11/23 17:31:23]

Yes, there is an install extension func in automation_provider that uses it.
That func itself is used by a ui test and an old version of chromedriver.

                                      ExtensionService* service,
                                      AutomationProvider* automation,
                                      int id,
                                      IPC::Message* reply_message);
+  // Creates an observer that replies using the JSON automation interface.
+  ExtensionReadyNotificationObserver(ExtensionProcessManager* manager,
+                                     ExtensionService* service,
+                                     AutomationProvider* automation,
+                                     IPC::Message* reply_message);
   virtual ~ExtensionReadyNotificationObserver();
 
   // Implementation of NotificationObserver.
@@ -349,11 +355,14 @@ class ExtensionReadyNotificationObserver
                        const content::NotificationDetails& details);
 
  private:
+  void Init();
+
   content::NotificationRegistrar registrar_;
   ExtensionProcessManager* manager_;
   ExtensionService* service_;
   base::WeakPtr<AutomationProvider> automation_;
   int id_;
+  bool use_json_;

[dennis_jeffrey, 2011/11/22 23:32:16]

nit: Should we move this down below the definition of reply_message_ below, to
separate the variables for constructor arguments from the other class variables?

[kkania, 2011/11/23 17:31:23]

Done.

   scoped_ptr<IPC::Message> reply_message_;
   const Extension* extension_;