Community
Participate
Working Groups
i think we could have a nice new option on the package explorer, like so: instead of showing the packages under each registered source folder on their own, it would be nice to also view them under a logic node named "combined source folders" or so. USE CASE we often separate diff. aspects of the code into diff. source folders which is a good thing. however, when u are unfamiliar with the code it has the drawback of having to navigate a lot more in the package explorer to find the package u want and look for. a unified view would help here quite a bit. i also would recommend to have a button for quick access.
Try the Java Browsing perspective. It does exactly that. Alternatively you can add the Packages view to your favorite perspective.
i understand that the packages view does that but IMO using that is cumbersome, since it only shows the packages but not its classes. that would be then another view. and having 3 views open to just see what's going on is a bit waste of screen real estate. switching between the perspectives would work but is more disruptive to coding, b/c u have to switch back again.
To just find a package in the PE, you can also use Navigate > Go To > Package... (that searches packages in the whole workspace, though).
thanks for pointing that, had never used it before... but the point is to have it all in view. i'm working around this issue now by a) having packeages linked to my editor and b) making it a fast view. with ctrl+3 i open that view now quickly still, it is not cutting it. maybe it's just me. i sense you are reluctant to do and hence i'll try to find some time to do it myself and will attach the patch here for future reference. but that may take a little time. can u hint me to the bundles and classes that i need to tweak for this?
The Package Explorer is implemented in PackageExplorerPart, but you also need changes in PackageExplorerContentProvider (and subclasses) to make sure all updates are still handled correctly, update the label provider, etc. You'd also need to add a custom node for the combined source folder, make sure that all actions still work with that node, and check all filters.
