Clean and create output directory when generating docs.

frog/lib/node/node.dart

Index: frog/lib/node/node.dart
diff --git a/frog/lib/node/node.dart b/frog/lib/node/node.dart
index 176609ef1e98e3f7f8709785b7a9460fcd21ce06..58b5dad5b60f1909469384af3d1298ab485ea7fa 100644
--- a/frog/lib/node/node.dart
+++ b/frog/lib/node/node.dart
@@ -90,6 +90,25 @@ class fs native "require('fs')" {
     native;
 
   static String realpathSync(String path) native;
+
+  static void mkdirSync(String path, [num mode = 511 /* 077 octal */]) native;
+  static List<String> readdirSync(String path) native;
+  static void rmdirSync(String path) native;
+  static Stats statSync(String path) native;
+  static void unlinkSync(String path) native;
+}
+
+class Stats native "fs.Stats" {
+  bool isFile() native;

[Jacob, 2011/11/16 19:59:30]

should these be

bool get file() native;
bool get blockDevice() native;
...
?

[jimhug, 2011/11/17 16:59:44]

This is a tough interop case and I'm unsure at which layer to make things more
dart-like.  For now, I think that we should stick with a direct clone of the
node apis here whenever possible and worry about the cleaner dart design when we
have an official shared complete file i/o library in dart.

On 2011/11/16 19:59:30, Jacob wrote:

[jacob314, 2011/11/17 19:06:16]

I agree that just reusing the node names and at most adding a TODO is the right
call.

On 2011/11/17 16:59:44, jimhug wrote:

[Bob Nystrom, 2011/11/17 20:44:21]

What Jim said. I was under the impression that this layer had to match node's
API exactly since it's using native here. NodeFileSystem then consumes this and
provides a Dartier API.

+  bool isDirectory() native;
+  bool isBlockDevice() native;
+  bool isCharacterDevice() native;
+  bool isSymbolicLink() native;
+  bool isFIFO() native;
+  bool isSocket() native;
+
+  // TODO(rnystrom): There are also the other fields we can add here if needed.
+  // See: http://nodejs.org/docs/v0.6.1/api/fs.html#fs.Stats.
 }
 
 class path native "require('path')" {