Fixed.
 xxxxx@xxxxx  2003-10-11There's a subtle user-interface issue with Next Class / Prev Class that
needs correcting. 

Clicking "Next Class" should go through all the interfaces in the current 
package alphabetically, and then all the classes alphabetically without
any separation (and without wrapping around to the start).  
"Prev Class" should go in the reverse direction.

As has been true since 1.0, Next/Prev iterates through
classes and interfaces separately.  In other words, you cannot
iterate continuously through classes and interfaces -- only 
classes or interfaces.  This is confusing.  Most people
would want and expect to be able to iterate through the entire
package. 

To be more specific, when you are at an interface page (not a class page) 
and click "Next", it takes you to the next alphabetic interface in that 
package.  When you hit the last interface you can't get to the classes.
To get to the classes, you have to go to the package summary and click
on a class, then "Next" takes you through the classes.

This is a bad design, because it's so difficult to get
from interfaces to classes.  Someone iterating through the classes 
might not realize that the interfaces were not included in that iteration.

N/A

Not a high priority, because these links are seldom used, but useful
to do someday.
 xxxxx@xxxxx  2001-03-01


As described, this would correspond to how the interfaces and then classes
appear in the lower left frame (when a package is selected in the upper
right frame).  In this case, Enums, Annotations, Errors and Exceptions 
should also be grouped in the order as shown in that frame.

Or should the classes and interfaces all be mixed together in a single
ordered list A-Z?  This would make more sense when the frame is not showing.

 xxxxx@xxxxx  2003-09-24

Fixed.
 xxxxx@xxxxx  2003-10-11