Bug 106708 - [EditorMgmt] tabs: Editor Master Tabs
Summary: [EditorMgmt] tabs: Editor Master Tabs
Status: NEW
Alias: None
Product: Platform
Classification: Eclipse Project
Component: UI (show other bugs)
Version: 3.2   Edit
Hardware: PC Windows XP
: P3 enhancement (vote)
Target Milestone: ---   Edit
Assignee: Platform UI Triaged CLA
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2005-08-10 22:30 EDT by Hans Zaunere CLA
Modified: 2019-09-06 15:30 EDT (History)
0 users

See Also:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Hans Zaunere CLA 2005-08-10 22:30:22 EDT
When working on multiple projects, it's very common to have large sets of files
open for each project.  However, switching between these files can become
tedious.  A way to group these open files, and thus the tabs in the editor,
based on arbitrary criteria, would be very useful.

It appears that the easiest way to do this would be to have a top-level tab, or
master tabs.  A top level tab could be expanded, perhaps in the Navigator area,
which would then have the open files previously worked on for that particular
project.  However, it should not be assumed that these master tabs be based
strictly on the project the file belongs to.  Common development tasks often
span multiple projects, so these master tabs should be able to have opened files
(ie, child tabs) move between them as needed.

Thank you, and if any clarification is needed I'm happy to provide.  I've
recently picked up Eclipse and already love it - keep up the great work guys.

Hans Zaunere
New York PHP
http://www.nyphp.com
Comment 1 Michael Van Meekeren CLA 2006-04-21 13:19:33 EDT
Moving Dougs bugs
Comment 2 Susan McCourt CLA 2009-07-09 19:08:00 EDT
As per http://wiki.eclipse.org/Platform_UI/Bug_Triage_Change_2009
Comment 3 Boris Bokowski CLA 2009-11-17 13:01:12 EST
Remy is now responsible for watching the [EditorMgmt] component area.
Comment 4 Eclipse Webmaster CLA 2019-09-06 15:30:41 EDT
This bug hasn't had any activity in quite some time. Maybe the problem got resolved, was a duplicate of something else, or became less pressing for some reason - or maybe it's still relevant but just hasn't been looked at yet.

If you have further information on the current state of the bug, please add it. The information can be, for example, that the problem still occurs, that you still want the feature, that more information is needed, or that the bug is (for whatever reason) no longer relevant.