Oxygen XML Forum

Hi there,
When I have my users install a new framework by downloading it and unzipping it into the frameworks dir, the new framework is appended to the list of Document Types as the last item. If my new framework is a customization of an existing framework (perhaps with a CustomRuleMatcher), this means that it cannot be used until the users also edit their settings, change their user role to Developer, and move the now framework to the top of the list.

Shouldn't newly added frameworks appear at the top of the list? I'd rather not require them to muck around in the settings in the Developer role.

Is there a workaround I don't know about?

Thanks,
David

Hello,

This is indeed a possible problem in the given situation.
I've added the problem to our issue tracking tool and we will try to accommodate this use case by adding the newly added custom frameworks to the top of the list.

Do note that in order to change the order of the frameworks it is not necessary to switch the user role to "Developer".


Possible workarounds:
1. Use a common Oxygen project file(.xpr) for all users via a version control repository(e.g. SVN) and keep the order of the Document Type Associations in the project options. Options -> Preferences -> Document Type Association, switch to "Project Options" and adjust the order of the document types/frameworks. The order of the document types/frameworks will be saved in the project file.

2. Use a custom frameworks directory with your own frameworks. You should copy and edit the catalog.xml and at least the XHTML 1.0 and 1.1 frameworks from the default Oxygen frameworks folder.
In Options -> Preferences -> Global, enable the option "Use custom frameworks directory" and browse for the folder where you keep your frameworks.

Regards,
Adrian

I'll give #1 a shot, though the tricky thing about #1 (which I'm already using for other settings) is that it's difficult to update existing projects. In the future, I'm thinking I'll have an xslt in the framework and button that they can push that runs that xslt over the current project to modify settings. That will work once I have the functionality implemented in the framework and have everybody using the framework. For now, there's a chicken-and-egg problem, so they have to manually promote the framework for now.

I suppose I could just replace the standard DocBook framework, but that just doesn't feel like a clean way to do it. I like the ability to process generic DocBook with the standard framework and documents that are based on our customized version of DocBook with our framework.

Thanks,
David

Hello,

This has been addressed in v12.2(to be released very soon). Newly added frameworks are now added at the top of the list(greater priority).

Regards,
Adrian

Excellent! Thank you for taking care of that so quickly.

David