Just a thought (we've been around this subject before), I've often found that when JavaDoc includes descriptive usage and examples that its really promotes rapid understandng of the packages for me personally. What are the current opinions on the following ideas?

1.) Javadoc = Userguide? Embed the userguide into the javadoc (though I know we want to start playing with MathML in the userguide, I know we've discussed issues with browser plugins and Javadoc generation that may possibly complicate this subject)

OR

2.) Use "crosslinks" throughout the Userguide and JavaDoc so they reference each other at specific points of interest.

-M.

--
Mark Diggory
Software Developer
Harvard MIT Data Center
http://www.hmdc.harvard.edu



---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]



Reply via email to