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

Side by Side Diff: frog/README.txt

Issue 10548047: Remove frog from the repository. (Closed) Base URL: https://dart.googlecode.com/svn/branches/bleeding_edge/dart
Patch Set: Move test and update apidoc.gyp. Created 8 years, 6 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 | « frog/.gitignore ('k') | frog/analyze.dart » ('j') | no next file with comments »
Toggle Intra-line Diffs ('i') | Expand Comments ('e') | Collapse Comments ('c') | Show Comments Hide Comments ('s')
OLDNEW
(Empty)
1 Frog is a dart compiler implemented in dart. It is currently focused on
2 compiling dart code to efficient and readable javascript code. However, it
3 is ultimately intended to be the basis for future code analysis tools and
4 development environments when these can be built in dart as well. Two
5 very early examples of this kind of use are in the samples directory:
6 * doc.dart - minimal documentation generator
7 * ifrog.dart - minimal command-line REPL for dart
8
9
10
11 To use frog:
12
13 1) Frog is now included in the checkout of the public repo of the bleeding_edge
14 branch. The code will be located under dart/frog.
15
16 2) From the dart/frog directory, run the presubmit script to check your
17 installation is all working.
18 frog$ ./presubmit.py
19
20
21 BEFORE YOU SUBMIT
22
23 Before you submit, you should:
24
25 1) Run the html tests:
26
27 $ ./frog.py --html -- tests/htmltest.dart
28 $ ./frog.py --html -- tests/canvastest.dart
29
30 These will open a browser -- verify in the console that no errors
31 happened.
32
33 2) Run the presubmit script:
34
35 $ ./presubmit.py
36
37 Note:
38
39 If you make any changes to files under tests, you are expected to ensure that
40 you don't break any of the other configurations. If you only change the status of tests for frog, you should be okay. However, if you
41 modify any of the tests themselves, please run the tests with both vm and
42 dartc configurations before checking in.
43
44
45 Details:
46
47 You can use build.py and test.py (that are run by the presubmit script):
48
49 $ ../tools/build.py --mode=release,debug
50 $ ../tools/test.py --report -t 5 -p color --mode=release --component=frog lang uage corelib leg
51
52 The 'frog' component is frog running on the VM.
OLDNEW
« no previous file with comments | « frog/.gitignore ('k') | frog/analyze.dart » ('j') | no next file with comments »

Powered by Google App Engine
This is Rietveld 408576698