- move a few functions to the prototype
- call bind() on the function that's used as a NodeVisitor
- for clarity, replace `currentParser` with `this` (made possible by
the previous changes)
- for consistency, move currentSourceName to the prototype
The three css files moved were not used by the default template. I only
had them there so the prettyPrintSource plugin would work. Since plugins
can use templates without ruining everything I've moved the css files to
their proper place and copy them over in
templates\prettyPrintSource\publish.js This makes it possible to enable
the plugin and get the same results with any template. Now all I need to
figure out is how to inject links to the generated pages into the
docs...
`cache` and `settings` are no longer private fields.
This was done so
that plugins could use this class without messing up
the final output
when template name collisions occur. i.e. each instance
has it's own
template cache. The `settings` were made specific to each
instance so
that users of this class could redefine the underscore
template
settings if they want to.
jake install[something/somewhere]
1) would give a warning that `path.existsSync` has been changed to
`fs.existsSync`. This has been updated.
2) would throw an error if there was no templates folder in the
extension being installed. Changed the condition on line 75 to check for
the existence of the correct item.
The new underscore template includes a tag sequence for escaping. I
added an override for that tag that is consistent with our overrides for
evaluation and interpolation.
Added filters for input end of line character where evilstreak/markdown
was called because it chokes on `\r\n`. We'll have to do this to any
input to this markdown parser unless/until they accept my pull request
and we update the upstream source.
https://github.com/evilstreak/markdown-js/pull/64
Technically, JSHint is only a dev dependency. But if you run `npm
install --dev git://github.com/jsdoc3/jsdoc.git`, npm tries to install
approximately every npm package that has ever existed, including many
that require gcc compilation.
This approach seems like the sanest workaround.
