Right. That's not a bad idea.
I've seen multi-row tabs for overflow. Ancient versions of Netbeans
(3.X) did this. It was pretty horrible over all. There were some
positive points, in the sense of being able to learn the position of
tabs for windows that were open for a long time, but overall, it was
confusing.
Current Netbeans, 4.X and 5.X *always* have a dropdown menu of all
open files on the right side of the window. It doesn't wait for the
tab bar to overflow, it just always shows the menu, which has the
advantage (as the menu is alphabetically sorted) that it's very
predictable. Of course, editing source code is different from browser
tabs. 50 browser tabs open would be exceptional. 50 source files in a
middling number to have open, and alphabetic sorting of source code
makes sense, whereas browser tabs probably need to be time ordered in
the menu.
Smooth scroll would be good. Current Netbeans scrolls 1 tab at a
time, which is way to slow and jerky. I like David's idea.
On Jun 14, 2006, at 12:56 PM, David Siegel wrote:
I think a great solution here consists in a compromise between
grouping tabs by rows and and using drop-down menus to access
individual tabs. Adding rows of tabs is appealing because it lets
us see many tabs easily at once, without having to click on rinky-
dinky menus on the periphery; however, users have come to expect
off-window UI access to come from such rinky-dinky menus. I propose
that when tabs overflow the window width, we add arrows to the left
and right edges of the tab bar, allowing a smooth scroll of either
half of the bar or the entire bar of tabs, bringing offscreen tabs
onscreen and vice versa. See Dashboard's widget tray for an example
- when you have more widgets than can fit on your screen, you get
those arrows that scroll the entire widget tray in a smooth motion.
David
On Jun 13, 2006, at 9:40 AM, Michael Watson wrote:
Can't agree more with this. Two rows of tabs is ridiculously
clunky and not like anything else in the OS that I can think of,
except crappy X11 apps.
For those who want to set Camino apart from said browser:
The drop-down arrow also did not originate with Safari, recall
that the toolbar itself started this convention, with an identical
UI widget for accessing additional toolbar buttons when the window
isn't wide enough. (See Preview for an easy example.)
--
mikey-san
On 12 Jun, 2006, at 20:44, Adam Randall wrote:
From an HIG standpoint, I don't think that makes sense. You'd
have to have a new bookmark "bar" for each line, and it'd get
kind of weird looking. The whole idea of a "tab" would probably
have to be reworked so it didn't look like a "tab" and probably
more of a bookmark like thing.
As for the drop-down at the right, that's a standard across the
OS, including Safari.
_______________________________________________
Camino mailing list
[email protected]
http://mozdev.org/mailman/listinfo/camino
_______________________________________________
Camino mailing list
[email protected]
http://mozdev.org/mailman/listinfo/camino
AndyT (lordpixel - the cat who walks through walls)
A little bigger on the inside
(see you later space cowboy, you can't take the sky from me)
_______________________________________________
Camino mailing list
[email protected]
http://mozdev.org/mailman/listinfo/camino
