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

..14-Feb-20134 KiB

.gitignore14-Feb-201338

AUTHORS14-Feb-2013292

init.js14-Feb-2013463

LICENSE14-Feb-20131.5 KiB

MODULE_LICENSE_BSD_LIKE_AND_APACHE_214-Feb-20130

NOTICE14-Feb-201311.5 KiB

README14-Feb-20131 KiB

script.js14-Feb-2013125.2 KiB

style.css14-Feb-20136.9 KiB

systrace.py14-Feb-20139.9 KiB

trace-viewer/14-Feb-20134 KiB

update.py14-Feb-20133.4 KiB

UPSTREAM_REVISION14-Feb-20134

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