Some equivalent for IWorkbenchOperationSupport ? [message #1450219] |
Wed, 22 October 2014 08:09 |
Thomas Elskens Messages: 159 Registered: September 2014 Location: Brussels - Belgium |
Senior Member |
|
|
Hello,
I was investigating the possibility to use the undo-redo operations with efxclipse and this package, while available, seems to be of little use without the IWorkbenchOperationSupport, needed to retrieve the IOperationHistory.
This OperationSupport resides in the package org.eclipse.ui.operations, which - if I'm not mistaken - is not available.
I hope till this point, my reasoning is correct?
And if it this, two little questions :
- is there some workaround or should I'd rather create a (series of) context function(s) to take care of (context-bound) commandstacks ?
- For the sake of my understanding of the Eclipse API: could I roughly consider that everything starting with "org.eclipse.ui" has to be replaced, in efxclipse, by an equivalent package org.eclipse.fx.ui, while the packages org.eclipse.e4.ui are ui-independent ?
|
|
|
Re: Some equivalent for IWorkbenchOperationSupport ? [message #1450249 is a reply to message #1450219] |
Wed, 22 October 2014 08:36 |
Thomas Schindl Messages: 6651 Registered: July 2009 |
Senior Member |
|
|
You need to create your own IOperationHistory and yes most likely
ContextFunction is the way to go.
If you create a bugzilla we can discuss there how a generic
implementation who is shipped as part of e(fx)clipse code look like.
On your second question:
a) org.eclipse.ui: bounds to SWT and bound to compat layer
b) org.eclipse.e4.ui: toolkit independent
c) org.eclipse.fx.ui: I'm a bit indifferent because we've not drawn a
clean line in this namespace, there are bundles in this namespace
who don't dependend on JavaFX and others who do
I think the general rule should be that org.eclipse.fx.ui is bound to
JavaFX.
I guess in this case the stuff we'd develop could even go into a none ui
package org.eclipse.fx.core.commands because it is not bound to any UI
at all!
Tom
On 22.10.14 10:09, Thomas Elskens wrote:
> Hello,
>
> I was investigating the possibility to use the undo-redo operations with
> efxclipse and this package, while available, seems to be of little use
> without the IWorkbenchOperationSupport, needed to retrieve the
> IOperationHistory.
> This OperationSupport resides in the package org.eclipse.ui.operations,
> which - if I'm not mistaken - is not available.
> I hope till this point, my reasoning is correct?
> And if it this, two little questions :
>
>
> is there some workaround or should I'd rather create a (series of)
> context function(s) to take care of (context-bound) commandstacks ?
> For the sake of my understanding of the Eclipse API: could I roughly
> consider that everything starting with "org.eclipse.ui" has to be
> replaced, in efxclipse, by an equivalent package org.eclipse.fx.ui,
> while the packages org.eclipse.e4.ui are ui-independent ?
|
|
|
Re: Some equivalent for IWorkbenchOperationSupport ? [message #1450268 is a reply to message #1450249] |
Wed, 22 October 2014 09:03 |
Thomas Schindl Messages: 6651 Registered: July 2009 |
Senior Member |
|
|
Another thing we could discuss is if we really want to use the
core.commands API or come up with something new more e4y ;-)
I general the problem is not that hard, you have a stack of commands and
undo/redo methods.
Tom
On 22.10.14 10:36, Tom Schindl wrote:
> You need to create your own IOperationHistory and yes most likely
> ContextFunction is the way to go.
>
> If you create a bugzilla we can discuss there how a generic
> implementation who is shipped as part of e(fx)clipse code look like.
>
> On your second question:
> a) org.eclipse.ui: bounds to SWT and bound to compat layer
> b) org.eclipse.e4.ui: toolkit independent
> c) org.eclipse.fx.ui: I'm a bit indifferent because we've not drawn a
> clean line in this namespace, there are bundles in this namespace
> who don't dependend on JavaFX and others who do
>
> I think the general rule should be that org.eclipse.fx.ui is bound to
> JavaFX.
>
> I guess in this case the stuff we'd develop could even go into a none ui
> package org.eclipse.fx.core.commands because it is not bound to any UI
> at all!
>
> Tom
>
> On 22.10.14 10:09, Thomas Elskens wrote:
>> Hello,
>>
>> I was investigating the possibility to use the undo-redo operations with
>> efxclipse and this package, while available, seems to be of little use
>> without the IWorkbenchOperationSupport, needed to retrieve the
>> IOperationHistory.
>> This OperationSupport resides in the package org.eclipse.ui.operations,
>> which - if I'm not mistaken - is not available.
>> I hope till this point, my reasoning is correct?
>> And if it this, two little questions :
>>
>>
>> is there some workaround or should I'd rather create a (series of)
>> context function(s) to take care of (context-bound) commandstacks ?
>> For the sake of my understanding of the Eclipse API: could I roughly
>> consider that everything starting with "org.eclipse.ui" has to be
>> replaced, in efxclipse, by an equivalent package org.eclipse.fx.ui,
>> while the packages org.eclipse.e4.ui are ui-independent ?
>
|
|
|
|
Powered by
FUDForum. Page generated in 0.03388 seconds