| Summary: | [Common Navigator] API request: setWorkingSet(s), getWorkingSet(s) | ||
|---|---|---|---|
| Product: | [Eclipse Project] Platform | Reporter: | Timotei Dolean <timotei_cluj> |
| Component: | UI | Assignee: | Platform UI Triaged <platform-ui-triaged> |
| Status: | CLOSED WONTFIX | QA Contact: | |
| Severity: | enhancement | ||
| Priority: | P3 | CC: | francisu, joeymink, oliver.buchtala, remy.suen |
| Version: | 3.7 | ||
| Target Milestone: | --- | ||
| Hardware: | All | ||
| OS: | All | ||
| Whiteboard: | stalebug | ||
|
Description
Timotei Dolean
I am working on a CMake (CDT) generator. Currently, I am studying the PDE documentation and found that remark about a missing working sets API. This would be the basic requirement for starting my plugin project. @Timotei: you are talking about some workaround using ISelection provider. Could you give me some detail (bear with me: I am PDE beginner). My context: I created a generator for CMake that can produce Eclipse projects for CMake enabled (C/C++) projects. Together, a working set specification is generated. I'd like to import this specification and set working sets automatically. Also, when I relaunch CMake these specification may change. So I'd like to have dynamic control over the working sets. I need this feature, right? Is there a workaround with your mentioned technique? Why is this issue restricted to platform PC Windows 7? This is something we can consider for 3.8. Right now the support for working sets is in the ProjectExplorer, not the CommonNavigator. I think there are several reasons to move the working set support down into the CommonNavigator. (In reply to comment #3) > This is something we can consider for 3.8. > > Right now the support for working sets is in the ProjectExplorer, not the > CommonNavigator. I think there are several reasons to move the working set > support down into the CommonNavigator. Ok. I am currently in a research phase sorting out feasibility of my project. Can I achieve my intent with the ProjectExplorer API? After playing around with examples, it seems that I ProjectExplorer (by controlling Window Working Sets) manipulation is sufficient for me. Thanks. (In reply to comment #5) > After playing around with examples, it seems that I ProjectExplorer (by > controlling Window Working Sets) manipulation is sufficient for me. Thank you, and you must have found the regular working set API that's independent of the ProjectExplorer. 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. If the bug is still relevant, please remove the stalebug whiteboard tag. |