• Home
  • History
  • Annotate
  • only in /external/chromium-trace/
NameDateSize

..21-Nov-20124 KiB

.gitignore21-Nov-201238

AUTHORS21-Nov-2012292

init.js21-Nov-2012463

LICENSE21-Nov-20121.5 KiB

MODULE_LICENSE_BSD_LIKE_AND_APACHE_221-Nov-20120

NOTICE21-Nov-201211.5 KiB

README21-Nov-20121 KiB

script.js21-Nov-2012125.2 KiB

style.css21-Nov-20126.9 KiB

systrace.py21-Nov-20129.9 KiB

trace-viewer/21-Nov-20124 KiB

update.py21-Nov-20123.4 KiB

UPSTREAM_REVISION21-Nov-20124

README

1The trace-viewer directory contains code from:
2
3    http://trace-viewer.googlecode.com/svn/trunk/
4
5The file UPSTREAM_REVISION contains the upstream revision number that was last
6pulled.  Changes should be made upstream and then pulled into the trace-viewer
7directory.
8
9The update.py script should be used to pull the latest upstream code, update
10the UPSTREAM_REVISION file, and package the CSS and Javascript files into
11style.css and script.js, respectively.  These generated files are being checked
12into the git repository, and they get embedded in each trace HTML file that
13systrace.py generates.
14
15To make development of trace-viewer code in the context of systrace easier,
16systrace supports arguments to generate HTML files that link to files in a
17trace-viewer development directory rather than embedding the JS and CSS in the
18HTML.  Do take advantage of this, you should check out the trace-viewer code in
19a new directory (e.g. trace-viewer-dev) and use systrace as follows:
20
21    $ ./systrace.py --link-assets --asset-dir trace-viewer-dev
22
23