| commit | c7c386446db323e3b5df17c162a24d3bc5330fb7 | |
| author | plundblad <plundblad@chromium.org> | |
| Thu, 16 Oct 2014 11:20:31 +0000 (16 04:20 -0700) | ||
| committer | Commit bot <commit-bot@chromium.org> | |
| Thu, 16 Oct 2014 11:20:49 +0000 (16 11:20 +0000) | ||
| tree | 5c261e254e22a8e82a1fc0cc477820884732e96f | treesnapshot (tar.gz zip) |
| parent | 294b9bbc0b244adac2fa5b88384ca3174d338e6b | commitdiff |
Support running ChromeVox in uncompressed mode and compress ChromeVox next by default.
By adding chromevox_compress_js=0 to your GYP_DEFINES, you can run
ChromeVox directly from its sources. The source files are symlinked
into the extension directory in the output directory. This is good for
faster development and debugging, but ChromeVox itself becomes slow
to load in this mode.
This also changes ChromeVox next to follow the same flag, hence being
compressed by default. When doing so, the classic background
page and ChromeVox next's background page are compiled together instead
of being loaded one after the other. This is necessary because they import
the same modules and the ones from Chromevox next will overwrite
the ones from classic after classic gets initialized.
Some of the targets in chromevox.gyp are consolidated. The main reason is
because many targets that copy or compress scripts need to have the whole
picture to not copy over the same files more than once
which is racy.
BUG=421136
Review URL: https://codereview.chromium.org/656813002
Cr-Commit-Position: refs/heads/master@{#299876}
By adding chromevox_compress_js=0 to your GYP_DEFINES, you can run
ChromeVox directly from its sources. The source files are symlinked
into the extension directory in the output directory. This is good for
faster development and debugging, but ChromeVox itself becomes slow
to load in this mode.
This also changes ChromeVox next to follow the same flag, hence being
compressed by default. When doing so, the classic background
page and ChromeVox next's background page are compiled together instead
of being loaded one after the other. This is necessary because they import
the same modules and the ones from Chromevox next will overwrite
the ones from classic after classic gets initialized.
Some of the targets in chromevox.gyp are consolidated. The main reason is
because many targets that copy or compress scripts need to have the whole
picture to not copy over the same files more than once
which is racy.
BUG=421136
Review URL: https://codereview.chromium.org/656813002
Cr-Commit-Position: refs/heads/master@{#299876}