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

Issue 10453097: Frog now called directly in dartdoc (Closed)

Created:
8 years, 6 months ago by Johnni Winther
Modified:
8 years, 6 months ago
CC:
reviews_dartlang.org
Visibility:
Public.

Description

Issue closed: Both frog and apidoc need updates to pass tests. Moving to use dart2js directly instead. Frog now called directly in dartdoc Changes: Usage print-out added. Check for missing entry-point added. Frog is now called directly and not via a process. This is part of a transition to move from Frog to Dart2js. BUG= TEST=

Patch Set 1 #

Total comments: 22

Patch Set 2 : Frog called directly from dartdoc #

Total comments: 4
Unified diffs Side-by-side diffs Delta from patch set Stats (+91 lines, -39 lines) Patch
M frog/minfrogc.dart View 2 chunks +8 lines, -5 lines 0 comments Download
M lib/dartdoc/dartdoc.dart View 1 9 chunks +83 lines, -34 lines 4 comments Download

Messages

Total messages: 4 (0 generated)
Johnni Winther
Frog is now called directly and not via a process. This is part of a ...
8 years, 6 months ago (2012-05-31 13:06:19 UTC) #1
ngeoffray
Drive-by comments http://codereview.chromium.org/10453097/diff/1/lib/dartdoc/dartdoc.dart File lib/dartdoc/dartdoc.dart (right): http://codereview.chromium.org/10453097/diff/1/lib/dartdoc/dartdoc.dart#newcode170 lib/dartdoc/dartdoc.dart:170: print('Documented ${dartdoc._totalLibraries} libraries, ' + You can ...
8 years, 6 months ago (2012-05-31 13:22:55 UTC) #2
kasperl
LGTM. Maybe Bob can tell us how he usually tests this? http://codereview.chromium.org/10453097/diff/1/lib/dartdoc/dartdoc.dart File lib/dartdoc/dartdoc.dart (right): ...
8 years, 6 months ago (2012-05-31 13:30:23 UTC) #3
Bob Nystrom
8 years, 6 months ago (2012-05-31 17:53:42 UTC) #4
Thanks for doing this!

There are two pieces you need to test this:

1. Test dartdoc directly. For this I just invoke the main dartdoc script and
throw it at a random codebase (usually itself), like:

  $ cd path/to/your/dart
  $ dart lib/dartdoc/dartdoc.dart lib/dartdoc/dartdoc.dart
  $ cd docs
  $ python -m SimpleHTTPServer

The last line is to get around file: over XHR limitations. Then point your
browser at localhost:8000. Click around a bit. If the docs look good, you're
good. Then:

2. Test apidoc. Apidoc is another program that uses dartdoc as a library and
extends it with some specific functionality we need for our main API docs. It's
what generates the docs you see at api.dartlang.org. To test:

  $ cd path/to/dart
  $ dart utils/apidoc/apidoc.dart
  $ cd docs
  $ python -m SimpleHTTPServer

Same deal. Click around and make sure stuff looks right. Errors are rarely
subtle. If it builds successfully and generates docs it's probably good.

http://codereview.chromium.org/10453097/diff/4/lib/dartdoc/dartdoc.dart
File lib/dartdoc/dartdoc.dart (right):

http://codereview.chromium.org/10453097/diff/4/lib/dartdoc/dartdoc.dart#newco...
lib/dartdoc/dartdoc.dart:128: final Future scriptCompiled =
compileScript(libDir,
Local variables don't need type annotations.

http://codereview.chromium.org/10453097/diff/4/lib/dartdoc/dartdoc.dart#newco...
lib/dartdoc/dartdoc.dart:147: [options] include
Nice!

http://codereview.chromium.org/10453097/diff/4/lib/dartdoc/dartdoc.dart#newco...
lib/dartdoc/dartdoc.dart:238: Future compileScript(String libDir, String
dartPath, String jsPath) {
Since this is no longer asynchronous, can you get rid of the future stuff and
just have main() call it directly before kicking off the other async operations?

http://codereview.chromium.org/10453097/diff/4/lib/dartdoc/dartdoc.dart#newco...
lib/dartdoc/dartdoc.dart:398: // conditions)
This worries me. I've never seen race conditions with this before. Do you know
what's causing it?

Powered by Google App Engine
This is Rietveld 408576698