Sean,
It's always fun to see people experimenting with ways to improve javadoc
output,
but in this case, there's something even more fun coming up, which will
make your
improvements somewhat unnecessary.
I'm referring to "javadoc search", JEP 225, http://openjdk.java.net/jeps/225
Although it
I've revisited replacing s with a AJAX + history.pushState
framework and thought I'd play around with the javadoc UI again.
You can see a current working prototype at:
http://playground.meekostuff.net/javadoc/jdk9/docs/api/overview-summary.html
Same notes and caveats as last time:
- this is a p
Thanks to people who have tried out javadoc-panner - either the bookmarklet
or the integrated javadoc-set at:
http://playground.meekostuff.net/javadoc/jdk8/docs/jdk/api/jpda/jdi/overview-summary.html
I should have explained that there is only this one modified javadoc set on
the site. If you have
## Framesets are simple, useful, familiar ##
Javadoc relies on HTML's for it's "FRAMES" view of doc sets.
This feature adds some convenient navigation whilst Javadoc's HTML output
remains as-simple-as-possible. It is familiar and useful and you wouldn't
abandon it unless an alternative was unques
