Bug 264370 - [package explorer] Add a "quick search" to the package explorer
Summary: [package explorer] Add a "quick search" to the package explorer
Status: RESOLVED DUPLICATE of bug 149110
Alias: None
Product: JDT
Classification: Eclipse Project
Component: UI (show other bugs)
Version: 3.4   Edit
Hardware: All All
: P3 enhancement (vote)
Target Milestone: ---   Edit
Assignee: JDT-UI-Inbox CLA
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2009-02-10 11:07 EST by Raphael Jolivet CLA
Modified: 2009-02-10 11:24 EST (History)
2 users (show)

See Also:

Attachments
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description Raphael Jolivet CLA 2009-02-10 11:07:23 EST 
Build ID: I20080617-2000

It would be really nice to have an optional "quick search" zone at the top of the package explorer, to easily find a file by typing a substring of it.

Navigating through files is always a tedious task and I find this very useful for application that provide it.

Typing in this input zone would filter the files of the project at once, dynamically, showing only the ones which match the filter (and expanding the tree accordingly to see them without needing extra action)

I have not been able to find a plugin that provides this functionality and I think it could save our time.

Thanks in advance for considering it.
Comment 1 Francis Upton IV CLA 2009-02-10 11:11:01 EST 
You want this for package explorer (which is part of JDT) or project explorer (which is part of the UI) or both?
Comment 2 Raphael Jolivet CLA 2009-02-10 11:14:53 EST 
Hello, thanks for your quick feedback !

I use package explorer more often, but it makes sense to have it on both, as this purpose also applies to the project explorer.
What do you think of the idea ?
Comment 3 Francis Upton IV CLA 2009-02-10 11:17:13 EST 
Please open another bug the for the project explorer.  I will more this one to JDT UI.
Comment 4 Dani Megert CLA 2009-02-10 11:24:53 EST 

*** This bug has been marked as a duplicate of bug 149110 ***