java - Restriction on org.eclipse.ui.internal.* classes -


We are developing a modeling environment as a plugin for Eclipse. It is possible to modify one of the approaches given to the user in this environment, i.e. to hide / show objects in the coolbar, menubar and scenes. When you are not developing the entire RCP-application, but it is difficult to modify only a plugin's visible coolbar- / menu etc. I was able to come up with the only solution to add an entry rule in the way of making Java org.eclipse.ui.internal * The package was to be available and later using the item with the coolbar manager / menu manager in the following example:

Workbenwindo Workbankwind = (WorkBankWindo) PlatformUI.getWorkbench (). GetActiveWorkbenchWindow (); Icoolbar Manager Coolbar Manager = Workbench Window. CottageManager2 (); IContributionItem [item] = coolbar manager .getItems (); (For IContributionItem item: item) {item.setVisible (wrong); }

However, by adding this access rule and then pressing the "restriction" alerts on each call to these packages, it seems a bit dirty.

So my question: why are these packages restricted and is there a better way of doing this?

Thanks, Leo


Comments

Popular posts from this blog

import - Python ImportError: No module named wmi -

Editing Python Class in Shell and SQLAlchemy -

lua - HowTo create a fuel bar -