I think Mustache templating would be a much better way to render the documentation output. The current way - concatenating strings and whatnot - is really not going to scale well.
I suggest something along the lines of:
Mustache templates are stored in /templates/, with each format having its own subdir, e.g. /templates/html/ and /templates/console/.
All rendering is done through Mustache templates and partials, so only a scope definition (class/module) should be rendered directly, as it will be responsible for rendering its own method definitions.
View/Presenter classes could be added to aid in the rendering.
So I "flipped the script" and created tomparse to handle the parsing. If you want to move forward with using mustache templates, then that would be great.
I think Mustache templating would be a much better way to render the documentation output. The current way - concatenating strings and whatnot - is really not going to scale well.
I suggest something along the lines of:
/templates/
, with each format having its own subdir, e.g./templates/html/
and/templates/console/
.Example
@defunkt: I would be willing to implement this if you were interesting in going down this route.