Jeff Ramsdale wrote:
On 1/8/07, Mark Brouwer <[EMAIL PROTECTED]> wrote:
...
Also I am of the opinion that the specs (was are no longer community
standards) should be maintained at the River project. Having the specs
at Jini.org can bring confusion and is extra work if you want to keep
them in sync.
Right. Keeping them in sync isn't what I was suggesting since I agree
that's extra work. Rather, maintaining them at Jini.org is what I was
proposing.
I've never been a fan of maintaining the specs in JavaDoc. I'd prefer
DocBook or the wiki or even HTML. But I'm not trying to reopen that
debate.
What I am wishing for, is a place to go to see all of the stuff linked together
and allowing discovery of buried information. With it all in Javadoc, you have
to know where to start with many things that you'd be able to read across if
there was a 'starting point' that linked everything together.
I don't know if that's a spec document, or a javadoc overview/guide or what.
But, somehow, there needs to be things you can find on the sun web site in those
tutorials on swing, security, JNLP etc that provide a way to wonder across
information that you might not know the terms (packages or classnames etc) to
use to find it in just javadoc.
Gregg Wonderly
