Community
Participate
Working Groups
FilteredTree uses JFace's ViewerFilter to filter nodes in the tree. This does not scale to arbitrary numbers of nodes for architectural reasons - refiltering requires a full refresh(), an operation that does not report progress and cannot be canceled even though it might be long-running. We should look at ways to make filterable trees available that don't freeze in refresh(). My current thinking is that this would involve filtering outside of the viewer, and that the resulting abstraction could end up in the data binding plug-in.
See bug 211578 for a real use case. Getting a new version of FilteredTree for 3.5 that does the filtering/searching in the background and can be canceled would be really nice.
With this, we might also avoid bug 186424.
Another use case in p2 is described in bug 256725. Ideally the solution would still look like FilteredTree from a code point of view. We had to subclass FilteredTree to deal with various check selection problems and to coordinate the refresh job and some of our jobs. If the solution involves data binding, it'd be great to have a migration example that shows how clients using FilteredTree would use the new support.
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.
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. As such, we're closing this bug. If you have further information on the current state of the bug, please add it and reopen this bug. 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. -- The automated Eclipse Genie.
