Bug 195579 - [Viewers] Should all tree/list viewers support in-place filtering?
Summary: [Viewers] Should all tree/list viewers support in-place filtering?
Status: CLOSED DUPLICATE of bug 69200
Alias: None
Product: Platform
Classification: Eclipse Project
Component: UI (show other bugs)
Version: 3.3   Edit
Hardware: PC Windows XP
: P3 enhancement (vote)
Target Milestone: ---   Edit
Assignee: Platform UI Triaged CLA
QA Contact: Hitesh CLA
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2007-07-05 15:34 EDT by Kevin McGuire CLA
Modified: 2010-05-07 09:17 EDT (History)
6 users (show)

See Also:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Kevin McGuire CLA 2007-07-05 15:34:12 EDT
The CVS repository view for platform has a ton of projects.  Often I'd like to quickly navigate to one and I know enough of the name to type in values into an filter dialog.  The same sometimes occurs for the project explorer.

Generally speaking, our lists have gotten quite long, yet we don't have a standardized way for the user to in-place filter them.  This is a different usage case than working sets, the former being for fast finding and quick/transient filtering, the latter for longer lived identification of resource.

Its worth considering whether all list/tree viewers should have an in-place filter (in which as you type it reduces the list of items shown).  We use this already in some places, such as the preferences dialog and some JDT quick views, but not consistently.

We'd also need to consider facilities for hiding the input box for cases where I don't need it and would like the space back (and to declutter the UI), as well as a declarative setting for whether it should be shown by default (e.g. some views are pretty well guaranteed to have short lists).
Comment 1 Boris Bokowski CLA 2009-11-26 09:53:50 EST
Hitesh is now responsible for watching bugs in the [Viewers] component area.
Comment 2 Dani Megert CLA 2010-05-07 09:17:44 EDT

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