| Extending swt-shell in another plugin [message #908467] |
Wed, 05 September 2012 12:36  |
|
Hi to anyone,
I have the following scenario:
plugin A - provides Shell
plugin B depends A - extends shell by adding button to add another command
How can I implement this feature?
Can I extend the shell with som mechanisms of application model or do I have to implement an extension point again?
Any help welcome
Best regards
|
|
|
|
| Re: Extending swt-shell in another plugin [message #909793 is a reply to message #909561] |
Fri, 07 September 2012 20:07  |
|
Hi Sopot,
thanks for your answer, I'll try it to ask in a more concrete way:
I have one plugin A, were I have a shell to edit users.
I have another plugin B, which should add a functionality to this user-shell, in this case a button were I can jump to another shell, were I can edit preferences of the currently selected user. This second shell is part of plugin B, but should not be coupled to plugin A.
I want the button only to be shown, when plugin B is installed otherwise the button should be not visible.
How do I implement this scenario with E4?
In E3.x I would have defined an extension point in plugin A for example. In plugin B I would implement this extension point. But I think in e4 extension points shall be replaced by the model and so my question is: Is there any technique in application model which can replace the extension points in this case?
Best regards
Markus
|
|
|
| Re: Extending swt-shell in another plugin [message #909809 is a reply to message #909793] |
Fri, 07 September 2012 20:56 |
 Thomas Schindl
Messages: 6651
Registered: July 2009 |
Senior Member |
|
|
No extension points at your own code is fine. What is replaced in e4 are
the many many extension points we had in e3 (views, menus, commands, ...).
There's nothing wrong we creating them for your own extension story.
Tom
Am 07.09.12 22:07, schrieb Markus Oley:
> Hi Sopot,
>
> thanks for your answer, I'll try it to ask in a more concrete way:
>
> I have one plugin A, were I have a shell to edit users. I have another
> plugin B, which should add a functionality to this user-shell, in this
> case a button were I can jump to another shell, were I can edit
> preferences of the currently selected user. This second shell is part of
> plugin B, but should not be coupled to plugin A.
>
> I want the button only to be shown, when plugin B is installed otherwise
> the button should be not visible.
>
> How do I implement this scenario with E4?
> In E3.x I would have defined an extension point in plugin A for example.
> In plugin B I would implement this extension point. But I think in e4
> extension points shall be replaced by the model and so my question is:
> Is there any technique in application model which can replace the
> extension points in this case?
>
>
>
> Best regards Markus
|
|
|
|
Powered by
FUDForum. Page generated in 0.02106 seconds
] 
Search
Help
Register
Login
Home
