-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Hi George, Thanks for that information. I've been looking into Oxygen's JWS kit and we will probably take that route. I didn't realize that the JWS version would use separate user settings from the full install. I had been wondering what happened with users who already were using the full Author. I wonder about what happens when the user changes some settings, and the I update some settings on the server. Are they merged? What happens if the user specifies one setting and I change that setting? I still think a case can be made for putting pretty-printing settings in the framework. But the question of "who wins" comes up again if the wants to specify something else. Perhaps the user could have a way to force his settings to override the framework if necessary? David On 10/03/2011 10:04 AM, George Cristian Bina wrote:
Hi David,
oXygen allows you to easily build a JavaWebStart distribution. Basically you get an all platforms distribution and configure that as you need and then run a script that packages everything as a JWS distribution (you will need a certificate to sign that). You can set a specific group of frameworks and your preferred global options, including formatting and profiling values. When the users will run that the provided options will be used - note that the users can still have normal oXygen installations that should have their specific set of options.
BTW, also the standalone version allows you to force a default set of global options, see http://www.oxygenxml.com/doc/ug-editor/topics/default-options.html
Best Regards, George -- George Cristian Bina <oXygen/> XML Editor, Schema Editor and XSLT Editor/Debugger http://www.oxygenxml.com
On 10/3/11 5:33 PM, David Cramer wrote: +1 for this feature request.
This reminds me of a similar request I have: the configuration of pretty-printing should be available at the framework level for a specific document type. In our organization, I want to control the pretty printing of "Rackbook" documents in the framework so that we're all producing xml wrapped at the same column width. However, I don't need or want to dictate the pretty-printing settings for other xml types that our users may use Oxygen for. Furthermore, there's no easy way for me to push changes to global or even project settings to all users.
Thanks, David
-----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.11 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/ iQEcBAEBAgAGBQJOiin1AAoJEMHeSXG7afUhPmAH/03595PD4bgRAGffy84XuPjJ /4GPXw8stNs/p/nuuqiNDv4PL0FvpkM8fO9q26/OrK1Y+2Z3IJ2QCWkZ3cp0ad1q 5j0eKQa9PxLrfaRAqVtSE3MJ88CspnINvsbWRIUubwWJCU0Ya714xpQzvexhEBka Xp7251+o4XNrvoHUuVERjRrLgzHWfvBaLLyw7v5duV9cJRioDF6x49pwieievWjN +sU5i2/vMhyCEdwzhAE+CzQnDphrue6hTta8CvocjSn38p/Nb29mAT6XfmhvqsL9 b/z+ia/vzsLKr9BXFQR1Z4cTAQKHTHQ551hKGS4XZ5KaA63qwIyrdubQbJYdZco= =OavI -----END PGP SIGNATURE-----