> From: Aaron M. Renn [mailto:[EMAIL PROTECTED]]
>
> [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.
>
OK, I'll just ignore Classpath for a bit and write a doclet that plugs into
Sun's Java. We can worry about the driver program when this is done.
> > 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.
>
I actually agree about frames, but I didn't see an alternative because for
some reason I was stuck on the idea of having the package navigation on the
left ... I hadn't looked at 1.1 for a while. Still, I like some of the
prettiness they have in 1.2 with tables. I think the no-frames version of
1.2, minus some of the frills, is a good way to do it.
Down to coding ...
--John Keiser
P.S. are we supposed to be using [EMAIL PROTECTED] or
[EMAIL PROTECTED]?
