Community
Participate
Working Groups
Build Identifier: All Filtering in various views, for example as dealt with in markers view, is purely a UI aspect and has less to do with the function of the view itself. As such, the feature/function belongs to UI domain regardless of the view being considered, and hence should be provided by a/the UI framework. See approach demonstrated in http://www.youtube.com/watch?v=0xpib6zhzv0. There are several benefits one may derive out this approach. For example, in markers views: 1) The attributes of a marker need not be fetched at least one *extra* time 2) And similarly, but not necessarily, we can do away with a few (java) references per attribute (per cell here) 3) The ready availability of such feature to the consumers of UI a. Code-reuse and its various advantages 4) If filtering happens at UI, it can make the view several times faster & smaller( in terms of memory). But without any numbers, I guess you’ll have to take my word for it :) 5) Provides for generic filter configurations and corresponding UI (and perhaps even more) There seems to be a plethora of newer techs emerging for UI (in fact under the very umbrella of eclipse.org), and it is likely that such effort may get perceived as wasteful. Still, IMHObservation, there are several apps that are based on the old code which do not have the slightest intention to move onto newer versions of the older stuff (my Android IDE for ex.). Interestingly, on the other hand, there are newer apps still being built or planned for the older techs :). Now, such apps could do away with quite a bit of code dedicated to the above-discussed purpose, and say that there has been something new and *promising* from eclipse.org. For folks who do not have much to do with newer eclipse technology, it is still the same old eclipse ;). Reproducible: Always Steps to Reproduce: 1. Open a view in the latest build of eclipse.
Created attachment 199374 [details] Mock-Up Screen-shot demonstrates point 5) in above comment.
Interesting :)
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.
