Bug 263012 - [Dialogs] Add FilterText composite to FilteredList
Summary: [Dialogs] Add FilterText composite to FilteredList
Status: NEW
Alias: None
Product: Platform
Classification: Eclipse Project
Component: UI (show other bugs)
Version: 3.5   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: 2009-01-30 04:50 EST by Tatiana Fesenko CLA
Modified: 2019-09-06 16:07 EDT (History)
1 user (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 Tatiana Fesenko CLA 2009-01-30 04:50:00 EST 
FilteredList control contains only List itself, but FilterText,which is always used together with FilteredList, is not defined in the control. FilteredText is defined in AbstractElementListSelectionDialog. It's very inconvenient, because if somebody wants to use functionality of the FilteredList without using Dialog, (s)he has to implement all FilteredText, renderers and so on. In other words, the user has to practically copy AbstractElementListSelectionDialog class, without extending Dialog.
On the other hand, FilteredTree composite, which is contained in the same package as FilteredList, contains FilteredText. And it makes is really usable.
Comment 1 Mike Wilson CLA 2009-05-05 12:51:15 EDT 
Changing Version tag to something more believable. Note that this is not a statement about when the enhancement request will be addressed (the Target Milestone field is used for that); the Version tag should be set to the version of Eclipse you were using when you saw the need for the enhancement.
Comment 2 Susan McCourt CLA 2009-07-09 18:20:23 EDT 
As per http://wiki.eclipse.org/Platform_UI/Bug_Triage_Change_2009
Comment 3 Eclipse Webmaster CLA 2019-09-06 16:07:06 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.