| How to restrict contributions or provide a list of 'granted' plugins. [message #466318] |
Tue, 17 April 2007 11:00  |
Eclipse User |
|
|
|
Originally posted by: valere.fedronic.ext.streamezzo.com
Hi,
I want to know if there is a standard way, for an rcp application, to
constrain the access, for example to the main tool bar (to avoid
unwanted contributions).
Is there a way to ignore an unwanted plugin (e.g. added in the rcp
'plugins/' dir) .
I know that this does not respect the plugin's philosophy.. but i don't
want my application to be such open.
valere.
|
|
|
| Re: How to restrict contributions or provide a list of 'granted' plugins. [message #466469 is a reply to message #466318] |
Thu, 19 April 2007 10:09  |
| Eclipse User |
|
|
|
Hi Valere,
There is no standard way to constrain access in the way you suggest. If a
plug-in is in the 'plugins' directory, it's extensions are going to get
loaded into the registry and menu options will show.
It is possible to use the Activities/Contributions framework to filter UI
elements out. There is also some exploratory work going on using XSL
transforms to manipulate plugin.xml files on startup.
http://wiki.eclipse.org/index.php/Product_Customization#Supp ressing_An_Action
This later approach is not easy and also requires you to run with the
-clean flag on at all times, which is not ideal.
Hope this helps,
--- Patrick
patrick@rcpquickstart.com
valere fedronic wrote:
> Hi,
> I want to know if there is a standard way, for an rcp application, to
> constrain the access, for example to the main tool bar (to avoid
> unwanted contributions).
> Is there a way to ignore an unwanted plugin (e.g. added in the rcp
> 'plugins/' dir) .
> I know that this does not respect the plugin's philosophy.. but i don't
> want my application to be such open.
> valere.
|
|
|
Powered by
FUDForum. Page generated in 0.35898 seconds
Home