diff options
author | Dan Beam <dbeam@chromium.org> | 2015-10-02 20:41:25 -0700 |
---|---|---|
committer | Dan Beam <dbeam@chromium.org> | 2015-10-03 03:42:50 +0000 |
commit | 99ce62a76a46f74ee31cd6dd1b28e05d3aafd2fb (patch) | |
tree | 4c71a14035bdcf40af873b15393c9d8c855c3925 /AUTHORS | |
parent | 395e4a2444b1e74c753cde3eb4de342e57bb2915 (diff) | |
download | chromium_src-99ce62a76a46f74ee31cd6dd1b28e05d3aafd2fb.zip chromium_src-99ce62a76a46f74ee31cd6dd1b28e05d3aafd2fb.tar.gz chromium_src-99ce62a76a46f74ee31cd6dd1b28e05d3aafd2fb.tar.bz2 |
Vulcanize new Material Design downloads UI
Vulcanize is a resource combiner written in node.js by the Polymer team
(authors CC'd). https://github.com/Polymer/vulcanize
Using it shaves a bit of time off the new MD downloads load time.
It'd be nice to integrate this into our build tooling so that if any
dependent files are modified, vulcanize + crisper would automagically
run. But this would require every Chrome engineer to have node.js + npm
(?) + vulcanize + crisper (a no go at the moment).
I'm going to propose depending on node.js in our build system soon,
but for now simply checking in the vulcanized + crisped output and
requiring folks that work on it to re-run the script (vulcanize.py)
doesn't sound too horrible.
The new way to open the non-vulcanized version is at:
chrome://downloads/dev.html
BUG=526577
R=michaelpg@chromium.org
TBR=phajdan.jr@chromium.org
Review URL: https://codereview.chromium.org/1378993003 .
Cr-Commit-Position: refs/heads/master@{#352233}
Diffstat (limited to 'AUTHORS')
0 files changed, 0 insertions, 0 deletions