bruce phipps wrote:
> Thanks, Johan. I have looked at those links.
> However, I would prefer a step-by-step tutorial on how to build
> Sun-style API docs starting from being given the code by a programmer.
Where else should it start? You are apparently missing how JavaDoc and
similar tools (doxygen, DOC++, etc.) work:
Someone (a programmer or a tech writer) places documentation in(!) the
source code. Using a thing called an editor

. In Java the standard is
that the API documentation is embedded in the source code, it is not
lying around separately. You just add a few additional HTML pages with
general descriptions if you feel like it. You feed the source code
through JavaDoc, and it generates all the nice web pages you are so keen on.
If you want to change the documentation, you drag that particular source
code out of the version control system, and edit the comments containing
the documentation. Then you run JavaDoc on the whole source code again.
When you are satisfied, you put the changed code back into the version
control system.
So you better brace yourself for having to deal with real programmers
and real source if you want to use JavaDoc documentation. Especially,
talk to them so you get the JavaDoc invocation added to the build system
instead of having to run it manually.
/Thomas