Provide ability to share team settings

[mgaerber]

Various settings (that would normally be stored in .xpr files) should be available through a central location.

Might be as easy as storing the .xpr file in the DB. To be investigated.

INFO from @raducoravu

Regarding the standalone Oxygen application, if you want to share settings you would have the following options:

1. Save the settings at project level and have all users use the same project ".xpr" file in the Project view when editing:

https://www.oxygenxml.com/doc/versions/17.1/ug-editor/#topics/sharing-projects.html

2. Provide a default options XML document to others:

https://www.oxygenxml.com/doc/versions/17.1/ug-editor/#topics/default-options.html

3. Have others manually import an options XML document:

https://www.oxygenxml.com/doc/versions/17.1/ug-editor/#topics/import-export-preferences.html

4. We have a Java API which would allow
   a plugin to impose fixed options when the application starts using the API:

PluginWorkspaceProvider.getPluginWorkspace().setGlobalObjectProperty(key, value);

In our Maven SDK we have a sample plugin called ImposeOptions which imposes a fixed set of options when the application starts.

[raducoravu]

The Oxygen Project view can open project configuration files only from the local drive. So option (1) would be usually used when you have a version control system and all users have a local workspace.