Chromium Code Reviews
chromiumcodereview-hr@appspot.gserviceaccount.com (chromiumcodereview-hr) | Please choose your nickname with Settings | Help | Chromium Project | Gerrit Changes | Sign out
(469)

Side by Side Diff: runtime/bin/vmservice/observatory/HACKING.txt

Issue 474083002: Update path to Observatory in HACKING.txt (Closed) Base URL: https://dart.googlecode.com/svn/branches/bleeding_edge/dart
Patch Set: Created 6 years, 4 months ago
Use n/p to move between diff chunks; N/P to move between comments. Draft comments are only viewable by you.
Jump to:
View unified diff | Download patch | Annotate | Revision Log
« no previous file with comments | « no previous file | no next file » | no next file with comments »
Toggle Intra-line Diffs ('i') | Expand Comments ('e') | Collapse Comments ('c') | Show Comments Hide Comments ('s')
OLDNEW
1 Dart Observatory Developer Guide 1 Dart Observatory Developer Guide
2 --- 2 ---
3 3
4 Assumptions: 4 Assumptions:
5 You are running pub from the latest dev channel release of Dart Editor. 5 You are running pub from the latest dev channel release of Dart Editor.
6 6
7 During development you do not need to run dart2js or rebuild the VM (unless 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 8 you are also making changes to the backend). While you're working on your
9 feature follow the steps: 9 feature follow the steps:
10 10
11 1. Open runtime/bin/vmservice/client in the Dart Editor 11 1. Open runtime/bin/vmservice/observatory in the Dart Editor
12 2. Run pub upgrade 12 2. Run pub upgrade
13 3. Run dart --observe script.dart 13 3. Run dart --observe script.dart
14 4. Run index.html in Dartium 14 4. Run index.html in Dartium
15 15
16 At this point you should see the initial Observatory UI and that 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. 17 it is communicating with the VM you launched in step 3.
18 18
19 Continue to develop and iterate until you're ready to upload your change 19 Continue to develop and iterate until you're ready to upload your change
20 for review. Upload your change and get an LGTM. 20 for review. Upload your change and get an LGTM.
21 21
22 5. Run pub build 22 5. Run pub build
23 6. Run ./deploy.sh 23 6. Run ./deploy.sh
24 24
25 Note: If you run pub from within the editor you need to make sure that it runs 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 26 in release mode (--mode=release), i.e., output is minified and does not include
27 any .dart source files. 27 any .dart source files.
28 28
29 At this point you should rebuild your VM and: 29 At this point you should rebuild your VM and:
30 30
31 7. Launch dart --observe script.dart 31 7. Launch dart --observe script.dart
32 32
33 In a non-Dart enabled browser navigate to localhost:8181 and ensure 33 In a non-Dart enabled browser navigate to localhost:8181 and ensure
34 that your feature works after being compiled to JavaScript. 34 that your feature works after being compiled to JavaScript.
35 35
36 8. Ensure the vm, standalone, and observatory unit tests still pass: 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 37 python tools/test.py --mode=debug --arch=ia32 --compiler=none --runtime=vm vm/cc standalone/vmservice vmservice
38 38
39 9. Commit your change 39 9. Commit your change
OLDNEW
« no previous file with comments | « no previous file | no next file » | no next file with comments »

Powered by Google App Engine
This is Rietveld 408576698