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 236941 - Grouping and collapsing tabs
Summary: Grouping and collapsing tabs
Status: NEW
Alias: None
Product: platform
Classification: Unclassified
Component: Window System (show other bugs)
Version: 8.0
Hardware: PC Windows 7
: P3 normal (vote)
Assignee: Stanislav Aubrecht
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2013-10-09 12:24 UTC by Eccenux
Modified: 2013-10-22 13:24 UTC (History)
0 users

See Also:
Issue Type: ENHANCEMENT
Exception Reporter:


Attachments
Two pinned, one collapsed group and two current tabs (65.33 KB, image/png)
2013-10-18 18:31 UTC, Eccenux
Details
Different approach (119.42 KB, image/png)
2013-10-22 13:24 UTC, Eccenux
Details

Note You need to log in before you can comment on or make changes to this bug.
Description Eccenux 2013-10-09 12:24:59 UTC
By grouping tabs I mean an ability to visually differentiate group and move it as a group and collapse it for later use. I don't mean creating new box with tabs (as you can do now) - creating a new box takes up space. Grouping state should also be saved in Project group (restored when switching between project groups).

How this could work:
1. You create a new group by dropping tab on another tab.
2. You add tabs to group by dropping tab on a group.
3. You collapse a group by a right click (and choose Collapse group from menu) or collapse button that could e.g. be on a side of grouped tabs.

How does that differ from Document Tab Group (boxes)
1. Collapsing should not destroy groups (like it does for boxes).
2. Only one tab is visible from all groups (and so doesn't take up space like separate boxes).
3. Open document document list should be shown as a tree (example below).
4. Grouping state should be saved in Project group (the state of windows/boxes is not, but I guess this might be a bug and not by design).

Tab tree example (this is a structure for both listing and maybe storage):
* DocumentNotInAnyGroup.txt
* AnotherDocument.md
* SomethingGeneral.java
* [Group]
** ElementInGroup.java
** AnotherApiElement.java
* [Group]
** AnotherGroup.js
** main.css
* AgainSomethingNotInAnyGroup.java
* AndAnother.js
Comment 1 Stanislav Aubrecht 2013-10-17 08:22:19 UTC
And what's the benefit of having such tab groups? Is this concept used in any other application?
Comment 2 Eccenux 2013-10-18 18:31:23 UTC
Created attachment 141276 [details]
Two pinned, one collapsed group and two current tabs

Yes, there are similar features in Opera 12. What's the benefit? It let's you organize work. Attaching example with collapsed group about SHA and some current stuff.

For example (real use case):
* One group for API that is created in Java by other people (and you may need to pick look from time to time, but not constantly).
* One group for shared JavaScript libraries that are really touched but I need to pick look from time to time.
* One group (or ungrouped) for current stuff in mobile application that is developed by me in JavaScript/PhoneGap.

Another use case:
* One group for common PHP files (like init.common.php, i18n/en.php).
* One group for database classes.
* current stuff ungrouped.

As you can see I tend to group by layers or subject (more or less). Currently I just move tabs to be close to each other but that process is slow and left most tabs are usually not visible.
Comment 3 Eccenux 2013-10-22 13:24:49 UTC
Created attachment 141411 [details]
Different approach

This one should be easier to implement. Groups could be simply tabs with tabs in them (visually similar to e.g. "Output" and "Search Results" tabs).

By default the name of the tab could be derived from last active tab (file) in group. Would make interface easier as no renaming would be needed.

You should be able to move files from one group to the other by dropping it on the other group tab. Opened files should open in active tab.