Home | History | Annotate | only in /external/chromium-trace
Up to higher level directory
NameDateSize
.gitignore20-Jun-201438
AUTHORS20-Jun-2014292
init.js20-Jun-2014460
LICENSE20-Jun-20141.5K
MODULE_LICENSE_BSD_LIKE_AND_APACHE_220-Jun-20140
NOTICE20-Jun-201411.5K
prefix.html20-Jun-2014791
README20-Jun-20141K
script.js20-Jun-2014250.8K
style.css20-Jun-201424.4K
suffix.html20-Jun-201452
systrace-legacy.py20-Jun-20149.7K
systrace.py20-Jun-20149.6K
trace-viewer/20-Jun-2014
update.py20-Jun-20143.4K
UPSTREAM_REVISION20-Jun-20144

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