Community
Participate
Working Groups
Once I have some feature started that I am working on, it would be great to be able to navigate around and see only the changed files which I am working on. How about a working set which contains all outgoing resources? This could also be a filter on top of whatever working set is currently selected. That way I could quickly toggle it, and it could be used in conjunction with other working sets. Or, it could be a working set which is a sub-type of the resource working set. Another type of unrelated mix-in which might be useful would be anything with a compile error. That way, if you touch a file and introduce a compile error, you could see both the outgoing change and the problems it would cause if released.
How about the following: 1. Create a synchronization for your entire workspace and switch it to outgoing mode. 2. The synchronize view shows error/warning markers now so you can see if you are releasing compile errors. But as far as using the existing working set mechanism to filter the packages/navigator view, that would be more involved. One problem with filtering existing views is that they don't support non-existing resources. We won't be able to show outgoing deletions.
I don't want to see outgoing deletions. I just want to see what I am currently working on (and any problems, in the case of errors), and outgoing changes is a rough approximation of this. Using the synchronize view is similar, but it's not quite the same.
I agree that this feature would be useful but this is not the intended use of working sets. To use working sets for this would be clunky at best (i.e. working sets are not intended to be dynamic). Therefore, it would be better as a filter. Unfortunately, at the current time, their is no mechanism for defining general filters that apply to all views. To do this, we would need a mechanism similar to the popupMenu objectContribution for registering filters with the workbench. This may have been included as part of the generic resource navigaotr work. We should investigate post 3.0.
I have created a Package Explorer filter which does exactly what I want. It works great. In addition to outgoing changes, the filter also shows anything with Errors in it (so that you know if your changes affected other classes). The main problem is that this is a single "filter" which must recognize both compiler errors and outgoing changes. You cannot create two filters and combine them additively. Also, workbench does not expect Filters to dynamically change, so there is no dispose() method on filter. I hooked the Control's dispose event to remove listeners added by the filter. Also, the filter doesn't know when it becomes disabled, so when any events are received it has to first check to see if it is enabled, and if not remove its listeners. Filters are a "glass half empty" approach. We need the opposite which I would call "providers". I'm using "provider" as a UI term and not an implmentation term such as Label/ContentProvider. When the packages view is populated, it would start with nothing, and allow providers to additively decide what should be viewed, and for filters to then decide what should get screened. Then, I would enable the following providers separately: 1) Outoing CVS changes 2) Compile Errors 3) Unshared projects/resource (local stuff).
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.
