> javadoc is HTML :) :-P Okay, let me rephrase: I think I can write HTML pages that are easier to understand and navigate than most javadocs.
> i really don't have any problem with javadoc format. I've never been a big fan. The format adds bloat (ex. Methods inherited from java.lang.Object are wait, wait, wait). Navigation by package does not highlight what is important in the big bag of classes. Heirarchies usually make sense AFTER you know where things fit in them. So for newbies, they do not know what they need to know, nor where to go looking for details. > we just need to be sure > we have docs somewhere that give an overview. these could be the > package.html, but i don't generally feel those are sufficient > or noticeable enough. > i'd rather keep overview type stuff to the dvsl docs. Agreed. Still wondering if we could somehow just create a special section in the javadoc comments that could be pulled 'up' into the DVSL docs automagically. Keep maintenance simple, and overview presentation a bit easier to read. Tim --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
