Chromium Code Reviews
chromiumcodereview-hr@appspot.gserviceaccount.com (chromiumcodereview-hr) | Please choose your nickname with Settings | Help | Chromium Project | Gerrit Changes | Sign out
(198)

Side by Side Diff: third_party/WebKit/Source/devtools/scripts/README.md

Issue 2464463002: Revert of DevTools: clean up scripts folder (Closed)
Patch Set: Created 4 years, 1 month ago
Use n/p to move between diff chunks; N/P to move between comments. Draft comments are only viewable by you.
Jump to:
View unified diff | Download patch
OLDNEW
1 # DevTools Scripts 1 # DevTools Scripts
2 2
3 ## Development workflow scripts 3 ## Python build scripts
4 4
5 These are scripts that can be useful to run independently as you're working on C hrome DevTools front-end.
6
7 The newer scripts such as for testing and hosted mode are written in Node.js, wh ich has become the standard toolchain for web apps. The older scripts such as bu ilding (e.g. bundling and minifying) are written in Python, which has first-clas s support in Chromium's infrastructure.
8
9 ## Overview
10
11 ### Folders
12
13 - build - Python package for generating DevTools debug and release mode
14 - chrome_debug_launcher - automagically finds Chrome Canary and launches it with debugging flags (e.g. remote debugging port)
15 - closure - see section on Closure Compiler below
16 - gulp - experimental build process written in node.js & gulp to remove the depe ndency on Chromium-specific build tools (i.e. gn and ninja)
17 - hosted_mode - run DevTools on a localhost development server
18 - jsdoc_validator - enforces the use of Closure type annotations
19 - local_node - installs a local runtime of node.js
20
21 ### Python Scripts
22 - convert_svg_images_to_png.py - manually run when adding svg images
23 - compile_frontend.py - runs closure compiler to do static type analysis 5 - compile_frontend.py - runs closure compiler to do static type analysis
24 - Note: the compiled outputs are not actually used to run DevTools 6 - Note: the compiled outputs are not actually used to run DevTools
25 - install_node_deps.py - installs node.js & npm modules
26 - lint_javascript.py - run eslint
27 - optimize_png_images.py - manually run when adding png images 7 - optimize_png_images.py - manually run when adding png images
28 8 - convert_svg_images_to_png.py - manually run when adding svg images
29 ### Node.js scripts
30
31 The easiest way to run the node.js scripts is to use `npm run` which displays al l the commands. For more information on the specific `npm run` commands, take a look at the primary devtools front-end readme (`../readme.md`).
32 9
33 ## Closure 10 ## Closure
34 11
35 DevTools manually rolls the closure compiler to ./closure. If you manually roll closure compiler, you will need to re-generate the closure_runner (in ./closure) and jsdoc_validator custom jars using the python scripts in their respective di rectory. Make sure you use JDK 7 to compile these jars, otherwise they won't run on buildbot. If you compile with JDK 7, anyone with Java 7 or Java 8 should be able to run the jar. 12 DevTools manually rolls the closure compiler to ./closure. If you manually roll closure compiler, you will need to re-generate the compiler-runner and jsdoc-val idator custom jars using the python scripts in their respective directory. Make sure you use JDK 7 to compile these jars, otherwise they won't run on buildbot. If you compile with JDK 7, anyone with Java 7 or Java 8 should be able to run th e jar.
OLDNEW

Powered by Google App Engine
This is Rietveld 408576698