Community
Participate
Working Groups
Bug to collect feedback on new working set support for package explorer.
Things already on the list: - improve the icon used for Java working sets - allow rearrange of working sets via Dnd and Copy/Paste - Show in Package Explorer shouldn't reveal elements in the Histroy working set
When swithing to the working set mode please make sure that there ins't any working set selected in "project" mode. Otherwise not all projects are shown.
I edit files from several projects. Since they appear in a flat list in the History ws I can't see where they come from (except by clicking on them an looking in the status bar). I'd like to see the full path either by grouping them by project or append the path to the name. Show In... is currently disabled but I'd like to select the file in the History ws and then Show in > Package Explorer. This needs the fix mentioned in comment 1. I am used to modify the working set settings via view menu (which is still the case when in 'Projects' mode), thereofre while History was is selected I expected to have view menu > Edit ==> allows me to uncheck some of the items. When in the 'Working Sets' mode: I have to use the context menu. This needs to be unified for the two modes. An option to filter stuff from History ws: e.g. I'd like to exclude projects which I don't work with but sometimes have to patch (e.g. because the don't compile without error). Currently I have to manually exclude the files after changing them.
1) Like Show In..., Link with Editor currently shows the CU in the History. Revealing the CU in the first Working Set it appears in would be better because one can put the most important WS on top. 2) Like Other Projects, a predefined All Projects WS would improve navigation in those cases where one is not sure whether the element of interest is in one of the user-defined WS or not.
*** Bug 80050 has been marked as a duplicate of this bug. ***
I removed an element from the History working set using the context menu. The element was removed correctly but was immediately re-selected in another working set it was defined within...not expected.
I work with my problems view set to filter on the selected resource and its children. When the working set item is selected in the package explorer, I would request that the errors/warnings contained within the working set would be displayed.
When a new class was added from synchronizing, it did not show up in the package explorer until I "showed" projects and then went back to the working set view.
Several operations applicable to sets of projects whould also make sense on a java working set in the package explorer: - Source actions - Compare with.../Replace with... actions - Team/Synchronize with Repository and possibly others
Regarding comment #9: Correct. This requires the new IResourceMapper support Team is working on. It went into yesterdays nightly build. So support has to wait until beginning M5. Darin, this also affects your request of focusing the problems view on a working set. I promipsed to much. We have to have the IresourceMapper support here as well.
- The "Other Projects" category should disappear if my existing working sets are collectively exhaustive. I.e., don't show it if it's empty. - It feels like special categories such as History and Other Projects should go at the bottom of the list rather than the top. This is especially true for "Other Projects", which presumably contains all the projects that I don't care about enough to define a working set on them. - "Other Projects" should have a different icon to make it clear that it's special. I went looking for the working set so I could delete it. - I have "Go into element on double-click" enabled on the Java Appearance preference page. This is not honoured on the working set elements in the package explorer (although it is still honoured for projects within the working sets).
Hi John, thanks for using the new feature and for the feedback. One comment: you can define your own order of the working sets in the package explorer my simple using DnD or by moving items up and down in the configuration dialog. Or do you suggest that when the configuration dialog opens the first time the history and other working set should appear at the bottom ? I will work on the other suggests in M5.
Sorry, I didn't realize I could sort the list manually. That's all I wanted.
Why are Resource working sets not included for optional display? I had defined a few and could not find them when I switched to the working set display; I only saw other and history. That had me thinking we had two kinds of working sets now, the old and the new. Finally hit me that I should try a Java working set. But given I might have some nice Resource working sets already defined (with Java and non-Java projects), it would be upsetting to see that I can't use them in the Package Explorer. Maybe the filter option for hiding non-Java projects should include non-Java working sets, that or a new filter just for working sets.
Showing resource working sets isn't easy to do. The problem is that if we support this the same resource can be shown as a Java element as a resource. This has a huge impact on all our actions. They currently assume that elements only appear in within one model, not in both.
Similar to comment 9, I would suggest to add the 'New' submenu to the context menu of working sets. For example, this would allow to put a newly created project automatically in the corresponding working set.
*** Bug 97197 has been marked as a duplicate of this bug. ***
*** Bug 97200 has been marked as a duplicate of this bug. ***
I have fixed the double click problem with go into. Resource working set can be used as well. Histroy working set is gone and team actions are available. Still missing is a better handling of the Other projects working set. I have opened bug 135008 to track this issue and will close this one. If you have other complains please file separate bug reports against JDT/UI.
