Revert "Replace create_standalone_js.py with a custom GWT linker"

README.md

 # DOM Distiller
 
 DOM Distiller aims to provide a better reading experience by distilling the
 content of the page. This distilled content can then be used in a variety of
 ways.
 
 The current efforts that are or will be powered by DOM Distiller:
 
 -   Reader mode: a mobile-friendly viewing mode for Chrome mobile
 -   [Simplify page for print]
@@ skipping 171 matching lines @@
 `ant` is the tool we use to build, and the available targets can be listed using
 `ant -p`, but the typical targets you might use when you work on this project
 is:
 
 -   `ant test` Runs all tests.
 -   `ant test -Dtest.filter=$FILTER_PATTERN` where `$FILTER_PATTERN` is a
     [gtest\_filter pattern]
     (https://code.google.com/p/googletest/wiki/AdvancedGuide#Running_a_Subset_of_the_Tests).
     For example `*.FilterTest.*:*Foo*-*Bar*` would run all tests containing
     `.FilterTest.` and `Foo`, but not those with `Bar`.
--   `ant gwtc` compiles .class+.java files to JavaScript. Standalone JavaScript
+-   `ant gwtc` compiles .class + .java files to JavaScript. Standalone JavaScript
     is available at `war/domdistiller/domdistiller.nocache.js`.
 -   `ant gwtc.jstests` creates a standalone JavaScript for the tests.
+-   `ant extractjs` creates standalone JavaScript from output of ant gwtc. The
+    compiled JavaScript file is available at `out/domdistiller.js`.
+-   `ant extractjs.jstests` creates a standalone JavaScript for the tests.
 -   `ant package` Copies the main build artifacts into the `out/package` folder,
     typically the extracted JS and protocol buffer files.
 
 # Contributing
 
 You can use regular `git` command when developing in this project and use `git
 cl` for collaboration.
 
 ## Uploading a CL for review
 
@@ skipping 170 matching lines @@
 ```bash
 distill http://example.com/article.html
 ```
 
 # Debug Code
 
 ## Interactive debugging
 
 You can use the Chrome Developer Tools to debug DOM Distiller:
 
--   Update the test JavaScript by running `ant gwtc.jstests` or `ant test`.
+-   Update the test JavaScript by running `ant extractjs.jstests` or `ant test`.
 -   Open `war/test.html` in Chrome desktop
 -   Open the `Console` panel in Developer Tools (**Ctrl-Shift-J**). On Mac OS X
     you can use **⌥-⌘-I** (uppercase `I`) as the shortcut.
 -   Run all tests by calling:
 
     ```javascript
     org.chromium.distiller.JsTestEntry.run()
     ```
 
 -   To run only a subset of tests, you can use a regular expression that matches
@@ skipping 70 matching lines @@
 aliases for easy access later. For example, Nexus 4 would be:
 
 ```
 --user-agent="Mozilla/5.0 (Linux; Android 4.2.1; en-us; Nexus 4 Build/JOP40D) AppleWebKit/535.19 (KHTML, like Gecko) Chrome/18.0.1025.166 Mobile Safari/535.19"
 ```
 
 Steps 1-3 in the guide above can typically be done in a stable version of
 Chrome, whereas the rest of the steps is typically done in your own build of
 Chrome (hence the "(Re)" in step 4). Besides speed, this also facilitates
 side-by-side comparison.