This Bugzilla instance is a read-only archive of historic NetBeans bug reports. To report a bug in NetBeans please follow the project's instructions for reporting issues.

Bug 67455 - [50cat] having Multiple layer of Tabs for Code editor
Summary: [50cat] having Multiple layer of Tabs for Code editor
Status: NEW
Alias: None
Product: platform
Classification: Unclassified
Component: Window System (show other bugs)
Version: 6.x
Hardware: PC Windows XP
: P3 blocker (vote)
Assignee: issues@platform
Keywords: UI
Depends on: 150393
  Show dependency tree
Reported: 2005-10-24 18:53 UTC by kalali
Modified: 2009-01-06 14:28 UTC (History)
2 users (show)

See Also:
Exception Reporter:


Note You need to log in before you can comment on or make changes to this bug.
Description kalali 2005-10-24 18:53:47 UTC
[ JDK VERSION : 1.5.0_03 ]

It is very good if code editor has multiple layer of Tabs for opened files.
There are some other feature which is good for this multiple Layer of tabs

0-it would be good if number of tab layer be configurable , and also number of tabs in each layer

1-It is good if all opened file could be re-ordered in tabs.
by reorder i mean user can move one tab near to another tab , for example to related file become side by side.

2-Auto-reorder is another feature , it means that Editor could automatically reorder the tabs
by "Most accessed first "  Order .It make it possible to switch between most accessed files more easier .

3-there should be some menu, shortcut,... which say : Close all tab expect X which X could be current tab.
Comment 1 kalali 2005-10-25 15:35:36 UTC
*3-there should be some menu, shortcut,... which say : Close all tab expect X
which X could be current tab.*

Actions of this kind could be the following:
1-Close Other Documents in Current Tab.
2-close all in current Tab ,
3-Close all Tabs : CTRL+SHIFT+F4 which now close all tabs
Comment 2 Miloslav Metelka 2005-10-26 13:17:43 UTC
Reassigning to core/ws for evaluation.
Comment 3 David Simonek 2005-10-26 13:37:39 UTC
Multiple layers of tabs are generally not recommended in UI books, they are even
trated as UI bugs, as they are more complicated and harder to use then just one
layer of the tabs.
Comment 4 David Simonek 2005-12-20 15:16:10 UTC
Hmmm, I don't see *any single* advantage of having multiple layers or tabs
instead of one layer. Netbeans used to have multiple layers and users were not
satisfied at all. Single layer is better because:
- eats *far less* screen real estate
- simpler
- visually more attractive and readable then multiple lines of tabs
- easier reordering

Auto-reorder which you mentioned is not related to multi layers, it can be done
with single tab layer as well.

Close all but current tab functionality is in the place as well now.

To sum it up, I don't see any advantage of having multiple tab layers, while
single layer have several mentioned advantages, so no plan to introduce multiple
tab layers back.
Comment 5 steve_taylor 2007-10-25 02:24:18 UTC
I would like to reopen this issue. I also want the option of multiple layers of tabs. Many people have adequate screen
real estate and enjoy the convenience. There is no need for the developers to force a single row on us just because they
don't like it, or worse, because a book told them that it's a sin.

So I propose that this feature be implemented with the user able to optionally set the maximum number of tab rows (it
could be unlimited), with the default setting at one row. Hopefully this keeps most people happy... except the zealots.

PS. The presence of this feature would give IntelliJ users another reason to migrate.
Comment 6 David Simonek 2008-10-22 10:14:10 UTC
Unfortunately having multiple rows of tabs in simply not an option in current editor tab implementation, as it is not
based on JTabbedPane and was designed specifically to be one line. Such rewrite is out of scope for us, sorry.

However, implementing multiple rows would be easy enough (for apps on top of the platform) if will be implemented.

However for NB IDE, we have no plans to work on it, so it's fair to welcome the community to work on this if interested,
patches are welcome.