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

..07-Jan-20164 KiB

.gitignore07-Jan-201651

agents/07-Jan-20164 KiB

AUTHORS07-Jan-2016292

LICENSE07-Jan-20161.5 KiB

MODULE_LICENSE_BSD_LIKE_AND_APACHE_207-Jan-20160

NOTICE07-Jan-201611.5 KiB

prefix.html07-Jan-20161.7 KiB

README07-Jan-20161 KiB

run_unittest.py07-Jan-20165 KiB

suffix.html07-Jan-201616

systrace-legacy.py07-Jan-20168.1 KiB

systrace.py07-Jan-20167.1 KiB

systrace_agent.py07-Jan-20161.6 KiB

systrace_trace_viewer.html07-Jan-20161.1 MiB

test_data/07-Jan-20164 KiB

trace-viewer/07-Jan-20164 KiB

update.py07-Jan-20162.1 KiB

UPSTREAM_REVISION07-Jan-201641

util.py07-Jan-20163.5 KiB

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