The inspiration for this suggestion comes from a posting by Ash on the
Rocket-gwt forum.
I guess ultimately the tabBar panel property should be public, rather than
limited to the selected Panel currently found in todays 4 *TabPanel classes.
The current implementation uses either a HorizontalPanel(for
Top/BottomTabPanels) or a VerticalPanel(for Left/RightTabPanels).
Ideally it should be possible to also use panels such as FlowPanel or a
panel that acts as what Ash describes below.
/// ash's post - start ///
oh i forgot. when i was going to port the swt ctabpanel to gwt there
was a feature that i really wanted to preserve. the java2script kit
supports too.
the best way i can describe it is as a "tab spinner" beside the last
displayed entry in the tab bar.
suppose that there are 50 tabs in a tab panel. i believe:
* the tab bar should _not_ render all 50 tabs and consume an unnessary
amount of client area
* the tab bar should render as many tabs within the client allocated
space. however, all other tabs can become accessible if scrolled via
the tab spinner.
i hope that made some sence man.
rgds ash
/// ash's post - end ///
Original issue reported on code.google.com by miroslav...@gmail.com on 3 Oct 2006 at 10:30
Original issue reported on code.google.com by
miroslav...@gmail.com
on 3 Oct 2006 at 10:30