| Jamie Gennis | 2da489c | 2012-09-19 18:06:29 -0700 | [diff] [blame] | 1 | The trace-viewer directory contains code from: |
| Jamie Gennis | 9279147 | 2012-03-05 17:33:58 -0800 | [diff] [blame] | 2 | |
| Jamie Gennis | 2da489c | 2012-09-19 18:06:29 -0700 | [diff] [blame] | 3 | http://trace-viewer.googlecode.com/svn/trunk/ |
| Jamie Gennis | d1270ce | 2012-05-06 13:27:13 -0700 | [diff] [blame] | 4 | |
| Jamie Gennis | 2da489c | 2012-09-19 18:06:29 -0700 | [diff] [blame] | 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. |
| Jamie Gennis | d1270ce | 2012-05-06 13:27:13 -0700 | [diff] [blame] | 8 | |
| Jamie Gennis | 2da489c | 2012-09-19 18:06:29 -0700 | [diff] [blame] | 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 | |