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

Side by Side Diff: dart/utils/tip/README.txt

Issue 10164004: Remove frogsh. (Closed) Base URL: https://dart.googlecode.com/svn/branches/bleeding_edge
Patch Set: Rebased Created 8 years, 8 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 | « dart/utils/tests/pub/pub.status ('k') | dart/utils/tip/toss.dart » ('j') | no next file with comments »
Toggle Intra-line Diffs ('i') | Expand Comments ('e') | Collapse Comments ('c') | Show Comments Hide Comments ('s')
OLDNEW
1 This is a rough experiment at more deeply integrating dart into a browser 1 This is a rough experiment at more deeply integrating dart into a browser
2 in order to simplify the dev experience. It currently provides a simple 2 in order to simplify the dev experience. It currently provides a simple
3 playground for interactively messing around with dart code and an extension 3 playground for interactively messing around with dart code and an extension
4 to chrome to automatically compile and run .dart files. The goal is to 4 to chrome to automatically compile and run .dart files. The goal is to
5 provide the infrastructure to build browser extensions to chrome and other 5 provide the infrastructure to build browser extensions to chrome and other
6 easily extensible browsers (such as FireFox) that will make it very easy to 6 easily extensible browsers (such as FireFox) that will make it very easy to
7 experiment with code and later full pages that incorporate the dart language. 7 experiment with code and later full pages that incorporate the dart language.
8 8
9 Note: All commands below must be run from the dart/frog directory. They have 9 Note: All commands below must be run from the dart/frog directory. They have
10 not been hardened for launch from other locations. 10 not been hardened for launch from other locations.
11 11
12 First, you need to build tip.js by hand - bootstrapping, ya'know. 12 First, you need to build tip.js by hand - bootstrapping, ya'know.
13 13
14 > ./frogsh --out=tip/tip.js --compile-only tip/tip.dart 14 > ./frog.py --out=tip/tip.js --compile-only tip/tip.dart
15 15
16 Then you need to start the local server: 16 Then you need to start the local server:
17 17
18 > ./frogsh tip/toss.dart 18 > ./frog.py tip/toss.dart
19 19
20 Finally, navigate to the appropriate page in chrome: 20 Finally, navigate to the appropriate page in chrome:
21 21
22 http://localhost:1337/frog/tip/tip.html 22 http://localhost:1337/frog/tip/tip.html
23 23
24 You should see the editor. 24 You should see the editor.
25 25
26 The part that sucks right now is that until we are properly bootstrapped, you 26 The part that sucks right now is that until we are properly bootstrapped, you
27 will need to rebuild tip.js by hand (the first step above) in order to see 27 will need to rebuild tip.js by hand (the first step above) in order to see
28 changes. 28 changes.
29 29
OLDNEW
« no previous file with comments | « dart/utils/tests/pub/pub.status ('k') | dart/utils/tip/toss.dart » ('j') | no next file with comments »

Powered by Google App Engine
This is Rietveld 408576698