Bob Kerns dc2ec62e70 Use the java facilities to handle path manipulations portably. ...

This was causing it to mis-calculate the paths, and end up losing the
output directory entirely, and overwrite the template static files
with themselves, resulting in truncation to zero-length. Of course,
they were also missing in the output.

It was expecting to be able to split paths on
System.getProperty("path.separator"), but that describes how to put a
path together, not how to take one apart, which is more complicated.

In particular, in windows, / is as valid a separator as \ in all but a
few UI contexts.

And since we need to pass / in paths that may get turned into URI's,
it's important to handle this correctly.

Java already provides a File facility to handle these sorts of operations.
This patch makes use of java.io.File to:

1) Find the parent of a File for dirname.
2) Find the name of a File for basename.

It also now makes use of substring for removing the ext for basename,
rather than Array.prototype.slice + join(""). I'm not sure what that
was all about...  It does have the effect of ensuring it's a Javascript
String, but calling String() has the same benefit and is much more clear.

You can put that back if there was a reason for it, but it looks just
confused to me.

2012-09-11 22:57:50 -07:00

..

jsdoc

make the tests pass again. note to self: run tests, THEN commit…

2012-09-09 21:15:58 -07:00

fs.js

make 'fs' and 'path' modules more consistent with Node.js

2012-08-19 15:25:02 -07:00

path.js

Use the java facilities to handle path manipulations portably.

2012-09-11 22:57:50 -07:00

sys.js

Use Rhino's require implementation.

2011-09-21 17:37:32 -06:00