Add web page replay to chrome_remote_control.

tools/gpu/page_sets/Q32012.json

Index: tools/gpu/page_sets/Q32012.json
diff --git a/tools/gpu/page_sets/Q32012.json b/tools/gpu/page_sets/Q32012.json
index d5b6b394c6723d93daa533d1041be25bf23db421..37382e0f2ad522984fddad4a590db87e8f2f1468 100644
--- a/tools/gpu/page_sets/Q32012.json
+++ b/tools/gpu/page_sets/Q32012.json
@@ -1,5 +1,6 @@
 {
   "description": "Pages hand-picked from top-lists in Q32012.",
+  "archive_path": "data/page_cycler/webpagereplay/2012Q3.wpr",

[nduca, 2012/09/21 06:35:50]

aw whoops, i totally named this file backward didn't i? Whommmp. Lets just
rename this stupid file to match your better convention?

One open question I have is where in the chrome path to put these files, if
we're going to have them shared between a page cycler and, say, gpu tests. In a
standalone case, I'd say tools/gpu/data/webpagereplay/.

Finally, what path is the archive_path relative to? David sort of set up a
convention in file:// protocols where its relative to the json file.

[tonyg, 2012/09/25 17:29:29]

Done
Seems pretty clean to just keep them in the page_sets dir. What do you think?
I made it relative to this file.

   "pages": [
     {"url": "http://www.facebook.com/barackobama"},
     {"url": "https://www.google.com/search?q=barack%20obama"},