OLD | NEW |
| (Empty) |
1 Dart Observatory Developer Guide | |
2 --- | |
3 | |
4 Assumptions: | |
5 You are running pub from the latest dev channel release of Dart Editor. | |
6 | |
7 During development you do not need to run dart2js or rebuild the VM (unless | |
8 you are also making changes to the backend). While you're working on your | |
9 feature follow the steps: | |
10 | |
11 1. Open runtime/bin/vmservice/observatory in the Dart Editor | |
12 2. Run pub upgrade | |
13 3. Run dart --observe script.dart | |
14 4. Run index.html in Dartium | |
15 | |
16 At this point you should see the initial Observatory UI and that | |
17 it is communicating with the VM you launched in step 3. | |
18 | |
19 Continue to develop and iterate until you're ready to upload your change | |
20 for review. Upload your change and get an LGTM. | |
21 | |
22 5. Run pub build | |
23 6. Run ./deploy.sh | |
24 | |
25 Note: If you run pub from within the editor you need to make sure that it runs | |
26 in release mode (--mode=release), i.e., output is minified and does not include | |
27 any .dart source files. | |
28 | |
29 At this point you should rebuild your VM and: | |
30 | |
31 7. Launch dart --observe script.dart | |
32 | |
33 In a non-Dart enabled browser navigate to localhost:8181 and ensure | |
34 that your feature works after being compiled to JavaScript. | |
35 | |
36 8. Ensure the vm, standalone, and observatory unit tests still pass: | |
37 python tools/test.py --mode=debug --arch=ia32 --compiler=none --runtime=vm vm/cc
standalone/vmservice vmservice | |
38 | |
39 9. Commit your change | |
OLD | NEW |