Bug 108966 - [EditorMgmt] tabs: Editor Sorter Widget
Summary: [EditorMgmt] tabs: Editor Sorter Widget
Status: NEW
Alias: None
Product: Platform
Classification: Eclipse Project
Component: UI (show other bugs)
Version: 3.2   Edit
Hardware: All All
: P3 enhancement (vote)
Target Milestone: ---   Edit
Assignee: Platform UI Triaged CLA
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2005-09-07 13:50 EDT by Terrence M Drozdowski 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 Terrence M Drozdowski CLA 2005-09-07 13:50:08 EDT
I came up with an idea that may help people like myself with sorting out the
large number of files I work with.  I always switch the editor to the single tab
view, that gives me the drop down of all the files I have open.  I know that I
can also access this via keyboard shortcut, and then type various filters to
prune the list down.  What would be nice to have, is a way to setup multiple
sorter lists, based on user defined types.  For example, if I could have 4
setup, one for *.java, another for *.jsp and yet another for *.xml and a final
one for Foo* that would make looking for files a bit easier.  Not sure if there
could be a way to 'pin' your favorite filters to the editor bar at the top, or
some other mechanism to easily access open files of your favorite/commonly used
type by filter.  Kind of a compromise between the single drop down and 40+ tabs
across the top.
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:09 EDT
As per http://wiki.eclipse.org/Platform_UI/Bug_Triage_Change_2009
Comment 3 Boris Bokowski CLA 2009-11-17 13:06:11 EST
Remy is now responsible for watching the [EditorMgmt] component area.
Comment 4 Eclipse Webmaster CLA 2019-09-06 15:30:50 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.