Looks good.
Agreed that the terminology and appearance should be the same on the
"All Classes" page as on a package page.
If space becomes an issue, I think the first tab could be reduced to
"All" provided there is a suitable heading above the table, such as "All
Classes and Interfaces" /"Classes and Interfaces in Package ..."
although even there, you could drop "in Package ..." given the context
of the package page.
Agreed that "All Classes" is less than ideal. It should either be "All
Classes and Interfaces" or just "All".
Just asking: does the "Classes" tab refer to "all classes, including
enum classes, record classes, exceptions and errors", or "all classes
except enum classes, record classes, exceptions and errors" ?
-- jon
On 4/12/21 8:59 AM, Hannes Wallnoefer wrote:
I have imlemented the tabbed classes and interfaces table and playing
around with the wording.
It looks like dropping the word „Summary“ would give us enough space
to actually expand the first „All Classes“ tab to „All Classes and
Interfaces“, which I find more meaningful and correct. That is even
with adding a „Record Classes“ tab which is currently missing on the
„All Classes“ index page.
Below is.a screenshot of how that would look like:
I would also suggest to use the same wording for the tabs on the „All
Classes“ index page and the package summary pages, as I don’t see why
they should be different.
Hannes
Am 10.04.2021 um 17:55 schrieb Jonathan Gibbons
<jonathan.gibb...@oracle.com <mailto:jonathan.gibb...@oracle.com>>:
I see we already have a similar table in the All Classes
page. Looking at that page I would suggest the following:
• Change the page heading to "All Classes and Interfaces"
• Change the first tab from "All Classes" to "All"
• Drop the word "Summary" from the other tabs
• Maybe pluralize all the tab names
-- Jon
