[
Date Prev][
Date Next][
Thread Prev][
Thread Next][
Date Index][
Thread Index]
[
List Home]
|
[handly-dev] Working set support (Re: Enabling working sets breaks the navigator)
|
Hi,
I have pushed to the master branch a set of base classes for working set support (Bug 458246).
You can use the latest integration build to give it a try. Here is the p2 repository:
I have tested the whole thing by implementing working set functionality for the Foo model in the Basic Example.
However, I'm reluctant to push the modified example code to the project's Eclipse repository, since, in my view, it would unnecessarily complicate what was meant to be "basic". I would rather prefer to include the working set functionality in a more advanced example planned for Handly 0.3.
That said, you can find the modified Basic Example with working set support in the topic branch 'workingset-example' of the 'handly-playground' repository on GitHub:
HTH,
Vladimir
Hi,
If adding to the navigator (as implemented in the examples) an actionExtension to "org.eclipse.ui.navigator.resources..*", which among other things enables working sets in the view, this extension resets the navigator's content provider input to the workspace. This means that the navigator loses all Handly-based content because that depends on the model being the navigator's input.
Do you have any suggestion about how to handle this? I tried different combinations of adapters (because I feel that being able to adapt IResources to IFooElements should be a solution), but couldn't make it work -- either it's not a good solution, or I did it wrong...
At some time in the future, one will probably want to support working sets anyway, so removing these extensions is only a temporary solution.
best regards,
Vlad
