Adding a LaunchApp command to Chromedriver

chrome/test/chromedriver/window_commands.h

Index: chrome/test/chromedriver/window_commands.h
diff --git a/chrome/test/chromedriver/window_commands.h b/chrome/test/chromedriver/window_commands.h
index 4e97ac9f1605a183f401a49da9bd9db8c8a9bed7..9ed0ffbff5b4d93f14f5da9ce409c9832e1e2ae8 100644
--- a/chrome/test/chromedriver/window_commands.h
+++ b/chrome/test/chromedriver/window_commands.h
@@ -39,6 +39,13 @@ Status ExecuteGet(
     const base::DictionaryValue& params,
     scoped_ptr<base::Value>* value);
 
+// Launches a Chrome App.
+Status ExecuteLaunchApp(

[chrisgao (Use stgao instead), 2014/01/15 21:39:56]

window_commands.cc/h are for commands that require a target window, like
navigating to a new url in the current target window, finding some element in
the page. If the target window was closed, we will return an error to the client
side. That's why the |WebView* web_view| is passed in and it won't be NULL.

session_commands.cc/h are for commands that require a session only. As long as
the session is not deleted, the command could be run.

"LaunchApp" seems to fall into the category of session_commands.cc/h.
Maybe we'd better move to those two files.

[bustamante, 2014/01/15 23:51:38]

Agree, Done.

+    Session* session,
+    WebView* web_view,
+    const base::DictionaryValue& params,
+    scoped_ptr<base::Value>* value);
+
 // Evaluates a given synchronous script with arguments.
 Status ExecuteExecuteScript(
     Session* session,