Name: krT82822 Date: 09/08/99


Suggestion: For the HTML page for a Java package, include
a link to the page for the parent package, and links to the
pages for any child packages.

I'm thinking of cases like javax.swing.tree (where the parent
package is closely related).

When looking at the page for javax.swing.tree, one is likely
to want to traverse up to javax.swing.

Also, looking at the page for javax.swing, subpackages
javax.swing.tree, javax.swing.text, javax.swing.table, etc.
might be of interest.

Currently, you have to traverse up to the package listing page,
scroll around just to find your context (the package you were
looking at), and click on the parent or child package.

(Well, as a real programmer I just edit the URL in my browser
if I don't feel like having to scroll around to find the link
I want, but links would be more convenient.)


This leads to an additional possibility for indexing at the
top level: List only top-level packages (so they all usually
fit in one page without scrolling), and allow traversing to
sub-packages through a package.

(I suggest that only as an _additional_ index. Showing all
package on the current overview-summary.html page is good
for looking around to see what's available.)
(Review ID: 94887)
======================================================================