Home | History | Annotate | only in /external/chromium-trace
Up to higher level directory
NameDateSize
.gitignore11-Dec-201338
AUTHORS11-Dec-2013292
init.js11-Dec-2013460
LICENSE11-Dec-20131.5K
MODULE_LICENSE_BSD_LIKE_AND_APACHE_211-Dec-20130
NOTICE11-Dec-201311.5K
prefix.html11-Dec-2013791
README11-Dec-20131K
script.js11-Dec-2013250.8K
style.css11-Dec-201324.4K
suffix.html11-Dec-201352
systrace-legacy.py11-Dec-20139.7K
systrace.py11-Dec-20139.6K
trace-viewer/11-Dec-2013
update.py11-Dec-20133.4K
UPSTREAM_REVISION11-Dec-20134

README

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