• Home
Name Date Size #Lines LOC

..--

agents/03-May-2024-557388

test_data/03-May-2024-3,9632,168

trace-viewer/03-May-2024-1,338,6241,256,770

.gitignoreD03-May-202451 54

AUTHORSD03-May-2024292 1311

LICENSED03-May-20241.5 KiB2827

MODULE_LICENSE_BSD_LIKE_AND_APACHE_2D03-May-20240

NOTICED03-May-202411.5 KiB206177

READMED03-May-20241 KiB2316

UPSTREAM_REVISIOND03-May-202441 21

prefix.htmlD03-May-20241.7 KiB7063

run_unittest.pyD03-May-20245 KiB12697

suffix.htmlD03-May-202416 32

systrace-legacy.pyD03-May-20248.1 KiB209184

systrace.pyD03-May-20247.1 KiB200151

systrace_agent.pyD03-May-20241.6 KiB6245

systrace_trace_viewer.htmlD03-May-20241.1 MiB4,7474,566

update.pyD03-May-20242.1 KiB6545

util.pyD03-May-20243.5 KiB11676

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