Adding a LaunchApp command to Chromedriver

chrome/test/chromedriver/client/chromedriver.py

Index: chrome/test/chromedriver/client/chromedriver.py
diff --git a/chrome/test/chromedriver/client/chromedriver.py b/chrome/test/chromedriver/client/chromedriver.py
index dccfde469e9b1905347c0b70618e68bc8e360a1e..10d8429aa0826ba76ad29a87fbf6c34a66e1370d 100644
--- a/chrome/test/chromedriver/client/chromedriver.py
+++ b/chrome/test/chromedriver/client/chromedriver.py
@@ -169,6 +169,9 @@ class ChromeDriver(object):
   def Load(self, url):
     self.ExecuteCommand(Command.GET, {'url': url})
 
+  def LaunchApp(self, app_id):
+    self.ExecuteCommand(Command.LAUNCH_APP, {'id': app_id})

[chrisgao (Use stgao instead), 2014/01/07 23:36:36]

If you do not plan to add an end to end test in
chrome/test/chromedriver/test/run_py_tests.py, you may revert
chrome/test/chromedriver/client/chromedriver.py and
chrome/test/chromedriver/client/command_executor.py. Because the python client
under chrome/test/chromedriver/client is for chromedriver developer only and not
for public users.

[bustamante, 2014/01/13 21:19:29]

Ok, Done.

+

[chrisgao (Use stgao instead), 2014/01/07 23:36:36]

And what's your plan for the change on the Java client side in the opensource
selenium project?

[bustamante, 2014/01/13 21:19:29]

It looks like org.openqa.selenium.chrome.ChromeDriver would be the place to go. 
I wanted to get this in first, and then tackle that.

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

Sounds good, thanks.

   def ExecuteScript(self, script, *args):
     converted_args = list(args)
     return self.ExecuteCommand(