Community
Participate
Working Groups
It would be nice if the Package Explorer had a text field at the top which would act like a filter for the visible projects. This would be similar to the filter in the preference pages.
On what elements would the filter work on? I assume on all elements in the tree, from projects to type and fields names. Only on the expanded elements or also on the not yet expanded elements? The last one difficult as it would require to open all files and parse the content. Or we have a index containing all elements. That's why we have the open type and open resources dialogs, which are both highly optimized as a all type search normally takes several seconds.
Maybe have settings so the user could choose projects, packages and/or types (filenames)? I wouldn't think that we would want it to go as deep as methods and fields... I would guess that would be an expensive calculation.
Stopping at packages (maybe even compilation unit) would make this a feasible request. But I'm not sure if users would understand this limitation. Wouldn't it look like a half-baked feature?
Perhaps, I guess it would depend on how users have their workbench set up. Personally I only go to the level of types in my Package Explorer and I use my Outline view to look at the fields and methods. I find if I dig deeper in the package explorer then it gets too cluttered. Maybe this is a better request for the Navigator view?
The navigator has been replaced by the project explorer, which would again have the problems with Java resources. I must say I also would like to see such a feature, best for all views. But the problem is really that the tree would have to be eagerly populated.
*** This bug has been marked as a duplicate of bug 149110 ***
