Summary: | [Working Sets] Enhancements for Working Sets | ||
---|---|---|---|
Product: | [Eclipse Project] Platform | Reporter: | Chris Noe <ChrisNoe> |
Component: | UI | Assignee: | Knut Radloff <knut_radloff> |
Status: | RESOLVED INVALID | QA Contact: | |
Severity: | enhancement | ||
Priority: | P3 | ||
Version: | 2.1 | ||
Target Milestone: | --- | ||
Hardware: | All | ||
OS: | All | ||
Whiteboard: |
Description
Chris Noe
2003-03-21 11:42:56 EST
1. duplicate of bug 15938 2. duplicate of bug 15941 3. should use filters for this, see bug 30578 4. a sort of working set hierarchy was suggested before, in bug 22493. What kind of hierarchy do you envision? Do you have a use case for this feature? I'm skeptical as nested working sets sound complicated. Chris, please read bug 37389 and comment whether that is the kind of working set hierarchy you have in mind (i.e., nested working sets). I would like to mark this bug as a duplicate of bug 37389 if this is indeed what you want. email exchange from 5/16: Chris: "Bug 35486 is really about integration with file operations in general. Hierarchical orgnaization is indeed covered well by 37389, but I think that's a separate issue." Knut: "Right, I think the file/resource interactions are adequately captured in the other bugs I mention. If I'm wrong and you have other concerns/suggestions please describe them in more detail in the bug." Closing this bug. The concerns are documented in bug 15938, bug 15941 and bug 37389. Please open specific bugs if you find other areas where working sets could be better integrated with resource (e.g., file) operations. |