Easier way to distribute profiling condition sets and Code templates

Hi, Sorry if this has been covered before. We are using Oxygen 15.2 and are currently using the global options to distribute profiling conditions sets and code templates to our writers as an options file which needs to be placed in their preferences folder. But I was wondering if there is a better way to do this preferably using the framework or any API option. Any help is greatly appreciated Thanks! Nathan

Hi Nathan, Oxygen 15.0 and newer has the API:
ro.sync.exml.workspace.api.PluginWorkspace.setGlobalObjectProperty(String, Object)
which allows you to forcefully set for example from a Workspace Access plugin preferences via the API. Actually this forum discussion is very close to what you want:
Starting with Oxygen 16.0 we added this API:
ro.sync.exml.workspace.api.PluginWorkspace.importGlobalOptions(File)
which allows you to forcefully set options to Oxygen from an options XML file (which was previously created by exporting options in another Oxygen installation). Based on this new API, our Plugins SDK now has a new sample plugin based on a Workspace Access Plugin extension called "Impose Options":
http://www.oxygenxml.com/oxygen_sdk.html#oXygen_standalone_plugins
Regards, Radu Radu Coravu <oXygen/> XML Editor, Schema Editor and XSLT Editor/Debugger http://www.oxygenxml.com On 6/4/2014 12:01 AM, Nathan wrote:
Hi, Sorry if this has been covered before. We are using Oxygen 15.2 and are currently using the global options to distribute profiling conditions sets and code templates to our writers as an options file which needs to be placed in their preferences folder. But I was wondering if there is a better way to do this preferably using the framework or any API option.
Any help is greatly appreciated
Thanks! Nathan
_______________________________________________ oXygen-sdk mailing list oXygen-sdk@oxygenxml.com http://www.oxygenxml.com/mailman/listinfo/oxygen-sdk
participants (2)
-
Nathan
-
Oxygen XML Editor Support (Radu Coravu)