On 7/25/07, [EMAIL PROTECTED] <[EMAIL PROTECTED]> wrote:
So does it make code easy to understand or not? Make your mind up!!
Well, that would depend on the quality of the documentation, not on JSDoc. :)
Personally, I do try and make use of it, but there are some limitations which I am attempting to work around by writing a script to run at a higher level. Also, code bloat is not a problem, as I run all CSS, HTML and JS through a compaction process as I take it live (automated release system) For most small projects it probably doesn't give much advantage, but I don't really understand how any of the arguments against using JSDoc are different to using JavaDoc.
Yep, you're right, the arguments aren't any different. But for those of us who don't have that extra step of compacting the code before deploying, we would have to add it in if we decided to use JSDoc. Whereas, for JavaDoc (and the other doc tools for other languages mentioned) you wouldn't have to worry about it, because the code is not as accessible to the end user as the Javascript because they're run server side or compiled. -- Ben Wong e: [EMAIL PROTECTED] w: http://blog.onehero.net ******************************************************************* List Guidelines: http://webstandardsgroup.org/mail/guidelines.cfm Unsubscribe: http://webstandardsgroup.org/join/unsubscribe.cfm Help: [EMAIL PROTECTED] *******************************************************************
