Comments on: JSDocs http://rfobic.wordpress.com/2009/06/11/jsdocs/ Somewhere in the middle of dreams & reality Mon, 14 Dec 2009 20:09:02 +0000 http://wordpress.com/ hourly 1 By: gozala http://rfobic.wordpress.com/2009/06/11/jsdocs/#comment-101 gozala Mon, 29 Jun 2009 07:32:15 +0000 http://rfobic.wordpress.com/?p=117#comment-101 Hi César, Thanks for your comment. At this point my tool is not that much flexible as well, but I'm definitely moving that direction. Currently in experimental branch I have some work done on rhino AST but it's not used by the tool yet. Feel free to fork me!! http://github.com/Gozala/jsdocs/tree/experimental Yes having flexible comment parser is something I would like to have as well, I was thinking to make comments parser / extractor being a plugin, that way it could be possible to write a different plugin which will process comments in a different manner. Hi César,

Thanks for your comment. At this point my tool is not that much flexible as well, but I’m definitely moving that direction. Currently in experimental branch I have some work done on rhino AST but it’s not used by the tool yet. Feel free to fork me!!
http://github.com/Gozala/jsdocs/tree/experimental

Yes having flexible comment parser is something I would like to have as well, I was thinking to make comments parser / extractor being a plugin, that way it could be possible to write a different plugin which will process comments in a different manner.

]]> By: César Acebal http://rfobic.wordpress.com/2009/06/11/jsdocs/#comment-100 César Acebal Sat, 27 Jun 2009 16:03:35 +0000 http://rfobic.wordpress.com/?p=117#comment-100 It seems very, very interesting. I'm currently considering which documentation tool to use for JavaScript and I'm quite frustrated: either they are very inflexible or not work at all when you start to do some 'complicated' things such as self-invocation anonymous functions, nested scopes and that sort of things. I've reached this page while looking for Rhino, source comments and similar keywords, since I think that the Rhino option is the only one available if we want the tool support any JavaScript construction, no matters how strange it be. I'll have a look at it, sure. Thank you very much for your efforts! By the way, couldn't it be possible make it even more flexible and allowing any documentation format (not just jsdoc). If you have done the tough work of extracting the comments from the source with the appropriate scope, it could be done delegating to some Formatter object. That will allow to use jsdoc but also, for example, restructured text to be passed to Sphinx or similar tools. It's just an idea. Thank you again! It seems very, very interesting. I’m currently considering which documentation tool to use for JavaScript and I’m quite frustrated: either they are very inflexible or not work at all when you start to do some ‘complicated’ things such as self-invocation anonymous functions, nested scopes and that sort of things.

I’ve reached this page while looking for Rhino, source comments and similar keywords, since I think that the Rhino option is the only one available if we want the tool support any JavaScript construction, no matters how strange it be.

I’ll have a look at it, sure. Thank you very much for your efforts!

By the way, couldn’t it be possible make it even more flexible and allowing any documentation format (not just jsdoc). If you have done the tough work of extracting the comments from the source with the appropriate scope, it could be done delegating to some Formatter object. That will allow to use jsdoc but also, for example, restructured text to be passed to Sphinx or similar tools. It’s just an idea.

Thank you again!

]]>