Some Eclipse Foundation services are deprecated, or will be soon. Please ensure you've read this important communication.
Bug 322659 - [Common Navigator] API request: setWorkingSet(s), getWorkingSet(s)
Summary: [Common Navigator] API request: setWorkingSet(s), getWorkingSet(s)
Status: CLOSED WONTFIX
Alias: None
Product: Platform
Classification: Eclipse Project
Component: UI (show other bugs)
Version: 3.7   Edit
Hardware: All All
: P3 enhancement with 1 vote (vote)
Target Milestone: ---   Edit
Assignee: Platform UI Triaged CLA
QA Contact:
URL:
Whiteboard: stalebug
Keywords:
Depends on:
Blocks:
 
Reported: 2010-08-13 10:15 EDT by Timotei Dolean CLA
Modified: 2019-11-27 07:31 EST (History)
4 users (show)

See Also:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Timotei Dolean CLA 2010-08-13 10:15:08 EDT
Build Identifier: 20100617-1415

Hello!
I would like to request API for handling with working sets programatically.
Currently, the deprecated IResourceNavigator has 2 methods: getWorkingSet and setWorkingSet. 
It would be nice for the CommonNavigator class to have those 2 methods for a better programatically handling of the working sets. Maybe even make them handle multiple working sets: IWorkingSet[] getWorkingSets(), setWorkingSets(IWorkingSet[] sets). 
I haven't found any other method of selecting/getting the active working sets without using my own ISelection provider.

Thanks.

Reproducible: Always

Steps to Reproduce:
Nothing to reproduce
Comment 1 Oliver Buchtala CLA 2011-04-30 15:53:35 EDT
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?
Comment 2 Oliver Buchtala CLA 2011-04-30 16:26:51 EDT
Why is this issue restricted to platform PC Windows 7?
Comment 3 Francis Upton IV CLA 2011-04-30 16:30:39 EDT
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.
Comment 4 Oliver Buchtala CLA 2011-04-30 16:39:40 EDT
(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?
Comment 5 Oliver Buchtala CLA 2011-04-30 18:58:52 EDT
After playing around with examples, it seems that I ProjectExplorer (by controlling Window Working Sets) manipulation is sufficient for me.

Thanks.
Comment 6 Francis Upton IV CLA 2011-04-30 19:30:20 EDT
(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.
Comment 7 Lars Vogel CLA 2019-11-27 07:31:18 EST
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.