Some Eclipse Foundation services are deprecated, or will be soon. Please ensure you've read this important communication.

Bug 363211

Summary: Feature Request - File Navigator Tab
Product: [Eclipse Project] Platform Reporter: Jens Stobernack <jstobern>
Component: IDEAssignee: Platform UI Triaged <platform-ui-triaged>
Status: CLOSED WONTFIX QA Contact:
Severity: enhancement    
Priority: P3 CC: remy.suen
Version: 3.7   
Target Milestone: ---   
Hardware: All   
OS: All   
Whiteboard: stalebug

Description Jens Stobernack CLA 2011-11-08 12:51:13 EST
Build Identifier: 20110916-0149

Hi,

I'm new to the forums so please be gentle on me. I've searched around for the answer to my request for quite some time and figured it is time to ask the community.

I've been using Eclipse based IDEs for some time and have recently move to Eclipse CDT native.

I am currently using:
Eclipse IDE for C/C++ Developers
Version: Indigo Service Release 1
Build id: 20110916-0149

I would like to request a new "Navigator" tab that displays all the files, in all the open projects, in a flat view. This new tab should allow for a "search" or "filter" so that the list of files is filtered.

Basically it would be similar to the "Open Resource" dialog box, but more permanent.

I know that I can use "customize view" on the project navigator but that is not flexible enough.

Ideally I would be able to select 2 files from this view and compare them.

Regards,
Jens.

Reproducible: Always
Comment 1 Remy Suen CLA 2011-11-17 11:14:40 EST
Seems to me as though this view could be extremely large.
Comment 2 Jens Stobernack CLA 2011-11-17 16:18:53 EST
(In reply to comment #1)
> Seems to me as though this view could be extremely large.

What do you mean by view? The stuff displayed in the tab window as results?

I would assume that it would be as large as the data which is available in the Project Explorer Tab (or view?) or the Navigator Tab (or view?)

The extreme case would be if the search (or filter) expression is *.

It would be great if the search field would be a regular expression.
Comment 3 Remy Suen CLA 2011-11-17 16:22:41 EST
(In reply to comment #2)
> (In reply to comment #1)
> > Seems to me as though this view could be extremely large.
> 
> What do you mean by view? The stuff displayed in the tab window as results?

Yes, that's what I mean. They're called views.

> I would assume that it would be as large as the data which is available in the
> Project Explorer Tab (or view?) or the Navigator Tab (or view?)

Right, but those views are usually not fully expanded at every single layer. At least, that's now how I use those views anyway.
Comment 4 Jens Stobernack CLA 2011-11-17 16:35:54 EST
(In reply to comment #3)
> (In reply to comment #2)
> > (In reply to comment #1)
> > > Seems to me as though this view could be extremely large.
> > 
> > What do you mean by view? The stuff displayed in the tab window as results?
> 
> Yes, that's what I mean. They're called views.

I see. Thanks.

> 
> > I would assume that it would be as large as the data which is available in the
> > Project Explorer Tab (or view?) or the Navigator Tab (or view?)
> 
> Right, but those views are usually not fully expanded at every single layer. At
> least, that's now how I use those views anyway.

Yes, I agree the initial view could be extremely large but the use case is to make the view extremely small. The idea would be that the view would get significantly smaller as the user enters an expression into the search field. Much like the Open Resource dialog starts trimming as you enter your search.

If the size of the view is an issue, then the view could have nothing displayed when the search criteria is blank.
Comment 5 Lars Vogel CLA 2019-11-27 07:34:22 EST
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.

If the bug is still relevant, please remove the stalebug whiteboard tag.