Yeah, I was thinking of having two multidocs for Commons/Jakarta. Stable and HEAD. I'll work on it a bit.
The inconsistent names need to be fixed by the projects themselves. I literally scrape off the top name of the Javadoc page :) Click on Codec stuff, it works for me in Firefox and Safari on the Mac. Possibly because the html file for that frame does not exist, so I'll make up a little blank one. Hen On Mon, 5 Jul 2004, Stephen Colebourne wrote: > Good work! > > Collections makes both HEAD and latest release available on its website. I > would think that it is the released javadoc that would be the one to focus > on first. > > The project names in the top left are also a little inconsistent!! > > Stephen > > From: "Gary Gregory" <[EMAIL PROTECTED]> > This is very nice! I'd personally like to use two views: "Released > Javadoc" and "CVS HEAD Javadoc". > > Gary > > > -----Original Message----- > > From: Henri Yandell [mailto:[EMAIL PROTECTED] > > Sent: Sunday, July 04, 2004 22:30 > > To: Jakarta Commons Developers List > > Subject: [general] Multidoc API of all Commons > > > > > > There's been a request on our Wiki for a combined javadoc for a while. > > Part of the request is that we improve our cross-referencing, which I > > think we can easily do, but will take a bit of planning. > > > > However, the other part is for a combined front-end (I think). I've > spent > > today hacking around a bit and have come up with: > > > > http://www.apache.org/~bayard/multidoc/index.html > > > > It's pretty easy maintenance, just give it a bunch of urls. Sorry > > CLI/FileUpload, your javadoc were not in the usual Maven place and I > > haven't tried hunting down correct ones yet. > > > > There's still effort needed to ensure we give it the right urls. Many > of > > the ones I quickly generated are in fact for developer javadoc, not > the > > released javadoc. It'd also be nice to modify the format somehow to > get > > more than one version of the same API in there. > > > > It's written/hacked in Java. I started to think about it in Perl, but > I > > prefer my Java scraping API too much to have to deal with something > that > > tries to parse HTML. It merely acts as a front end to existing > javadoc; so > > should be easy to grow to cover other parts of Jakarta/Apache > (ECS/ORO?). > > > > Currently it's all static, so after a bit of cleaning it would quite > > easily be something that could be hooked up to the Commons site. I'd > like > > to put a dynamic search in there, but that can come later. > > > > Anyway, any thoughts and opinions would be gratefully received, > > > > Hen > > > > > > --------------------------------------------------------------------- > > To unsubscribe, e-mail: [EMAIL PROTECTED] > > For additional commands, e-mail: [EMAIL PROTECTED] > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
