Page 1 of 1
Using version control with Author
Posted: Sat May 11, 2013 1:42 am
by runleonarun
I actually have a few questions:
1. Is there a best practice for version controlling Author so we can save things like transformation changes and share them with team members?
2. We are exploring the idea of using Author to generate html5 output, do you have examples from customers who are doing this?
3. What is the cost of upgrading from Author to Editor?
Thanks for any help!
Re: Using version control with Author
Posted: Tue May 14, 2013 5:44 pm
by adrian
Hello,
1. For sharing options and transformation scenarios between team members, we recommend using 'Project options' and 'Project scenarios' and a project file (.xpr) that's available on the version control system (e.g. SVN) to all the team members.
Every team member will have a local working copy from the version control system and each member will use the project file(.xpr) from his/her local copy. This project file contains all the options and scenarios that are necessary for that particular project. Then all you would have to do is adjust/add/remove the project options/scenarios, commit the project file to the repository and tell the team members to simply update their project file from the repository(or even script this at every startup). This way everyone could share in a non intrusive way the options and the scenarios.
The project options can be triggered in each option page (so they can be selective) from Options > Preferences.
The scenarios are by default stored in the project but they can be selectively stored/moved between the global options and the project options: Document > Transformation > Configure Transformation Scenario dialog or the Transformation Scenarios view (Window > Show View > ...) . Right click on the column headers and select Show "Storage" so you can verify where each scenario is stored. To change the storage location, select multiple scenarios, right click and pick Change storage.
The same rules apply to the validation scenarios: Document > Validate > Configure Validation Scenario
2. Unfortunately AFAIK we do not currently have such examples from customers.
Currently (v14.2) Oxygen does not provide for the supported document types (DITA, DocBook, etc) out-of-the-box transformations that publish to HTML5. But it is of course possible to use custom transformations that do this.
3. There is no readily available upgrade path from Author to Editor. However, you can contact our sales department and they will help you with this. Please write to sales AT oxygenxml DOT com and provide information of your purchase and the number of licenses that you want to upgrade/convert.
Regards,
Adrian