[EMAIL PROTECTED] ([EMAIL PROTECTED]) wrote:
> How much of JavaDoc is done? Would I just have to make a Classpath
> Doclet in order to get everything working (minus any bugs that turn up
> in our implementation of the Doclet API)? Or is there more core stuff
> to implement with regards to JavaDoc?
As I said, some sort of driver program also needs to be written. I would
put this off till last though. Right now a doclet to generate HTML is
probably the next logical step.
> Suggestions for look-and-feel are welcome. It is going to be different
> than Sun's, I'm pretty sure, but it won't be different just for the sake
> of being different. It will probably use a two-frame model, one for
> navigation and one for displaying the class documentation (so that class
> documentation pages aren't cluttered, for printing purposes).
I personally despite frames. I would much prefer something close to what
the Java 1.1 docs look like. Copying Sun's look and feel is probably also
the easiest way to go because the design work is already done.
--
Aaron M. Renn ([EMAIL PROTECTED]) http://www.urbanophile.com/arenn/
