Page 1 of 1

Oxygen Customization

Posted: Tue Mar 26, 2019 1:03 pm
by Anvesh
Hi,

We customize oxygen menus for our project purpose. We have taken oxygen 20.1 and we found out there are extra three menu items which we need to customize.

Below are the menu items which we need to customize :
1. File > Open URL
2. Help > Report Oxygen problem
3. Help > Support Tools > Randomize XML Text Content

But there are a few challenges that we are facing right now. Earlier we customized open URL option with its identifier (com.oxygenxml.editor.urlsupport.openURL), but now we still could see this option.

These are the other two options identifiers
com.oxygenxml.editor.actions.actionSet.randomizeXmlTextContent
com.oxygenxml.report.actionset.reportProblem

Now, while using these identifiers we are not able to remove the options.

Could you please suggest a solution or an alternative on this issue.

Thanks in advance !

Regards,
Anvesh

Re: Oxygen Customization

Posted: Tue Mar 26, 2019 4:31 pm
by Radu
Hi Anvesh,

Are you customizing the Oxygen XML Editor or XML Author Eclipse plugin?
If you open Oxygen's "plugin.xml" there is an "org.eclipse.ui.menus" extension point where all our contributions are added to the menus, including those 3 actions added to the main menu. So that's how our plugin adds the actions.
Can you tell me what exactly you are trying to do on your side to remove these extension points added by our plugin? Are you editing our plugin.xml directly?

Regards,
Radu

Re: Oxygen Customization

Posted: Wed Mar 27, 2019 4:44 pm
by Anvesh
Hi Radu,

We are customizing XML Author Eclipse plugin.
We are trying to remove the three options which I mentioned earlier. Previously we used to build a deployable jar by customizing unnecessary items based on our need.
But when tried the same method for the new menu items it is not reflecting through plugin.
Can we directly modify plugin.xml based on our need, as it makes our work easier
Please suggest!

Regards,
Anvesh

Re: Oxygen Customization

Posted: Thu Mar 28, 2019 9:38 am
by Radu
Hi Anvesh,

So you mentioned:
Previously we used to build a deployable jar by customizing unnecessary items based on our need.
How exactly did you do that? As I do not know what previously worked it's hard for me to help.
Of course you can also manually edit our plugin.xml if you plan to manually deploy a copy of our plugin instead of having end users download our plugin from our web site.

Regards,
Radu