Customizing only specific default options in a JWS installa
Post here questions and problems related to oXygen frameworks/document types.
-
- Posts: 16
- Joined: Fri Mar 20, 2015 2:29 pm
Customizing only specific default options in a JWS installa
I'm trying to specify default options to be automatically installed with the application (using JWS) and there's something that isn't clear to me. I've read http://www.oxygenxml.com/doc/ug-oxygen/ ... tions.html that explains how to provide a full set of new default options, which is fine.
But I only want to change the default value of a handful of options (5-6 at most), while the exported option file contains all the settings, which may even change in later versions and in general I don't want to be concerned with them.
If I cut down the exported options xml to only contain the options that I want to override, can I expect the rest to be set to whatever values the application is originally shipped with? Or is there a better way to achieve the same effect?
But I only want to change the default value of a handful of options (5-6 at most), while the exported option file contains all the settings, which may even change in later versions and in general I don't want to be concerned with them.
If I cut down the exported options xml to only contain the options that I want to override, can I expect the rest to be set to whatever values the application is originally shipped with? Or is there a better way to achieve the same effect?
-
- Posts: 9434
- Joined: Fri Jul 09, 2004 5:18 pm
Re: Customizing only specific default options in a JWS inst
Hi,
So you would have the following options:
1) Remove from the exported XML the keys which are not necessary.
2) You could minimize the number of saved option keys by first using from the Options menu the Reset Global Options action, then check only those options you are interested in and then export them to XML.
3) If all those options you want to send as defaults are saved in preference pages, you can create a new project in the Project view, then in the Preferences switch those preference pages where the modified setting are to project level. Then as suggested in the user guide topic you quoted above you need to preserve the ".xpr" extension on the project file and refer to it in the JNLP:
Regards,
Radu
So you would have the following options:
1) Remove from the exported XML the keys which are not necessary.
2) You could minimize the number of saved option keys by first using from the Options menu the Reset Global Options action, then check only those options you are interested in and then export them to XML.
3) If all those options you want to send as defaults are saved in preference pages, you can create a new project in the Project view, then in the Preferences switch those preference pages where the modified setting are to project level. Then as suggested in the user guide topic you quoted above you need to preserve the ".xpr" extension on the project file and refer to it in the JNLP:
Code: Select all
<property name="oxy:com.oxygenxml.default.options" value="http://host/path/to/default-options.xpr"/>
Radu
Radu Coravu
<oXygen/> XML Editor
http://www.oxygenxml.com
<oXygen/> XML Editor
http://www.oxygenxml.com
Return to “SDK-API, Frameworks - Document Types”
Jump to
- Oxygen XML Editor/Author/Developer
- ↳ Feature Request
- ↳ Common Problems
- ↳ DITA (Editing and Publishing DITA Content)
- ↳ SDK-API, Frameworks - Document Types
- ↳ DocBook
- ↳ TEI
- ↳ XHTML
- ↳ Other Issues
- Oxygen XML Web Author
- ↳ Feature Request
- ↳ Common Problems
- Oxygen Content Fusion
- ↳ Feature Request
- ↳ Common Problems
- Oxygen JSON Editor
- ↳ Feature Request
- ↳ Common Problems
- Oxygen PDF Chemistry
- ↳ Feature Request
- ↳ Common Problems
- Oxygen Feedback
- ↳ Feature Request
- ↳ Common Problems
- Oxygen XML WebHelp
- ↳ Feature Request
- ↳ Common Problems
- XML
- ↳ General XML Questions
- ↳ XSLT and FOP
- ↳ XML Schemas
- ↳ XQuery
- NVDL
- ↳ General NVDL Issues
- ↳ oNVDL Related Issues
- XML Services Market
- ↳ Offer a Service