<oXygen/> XML Editor helps you organize your XML-related files into projects. In this way, you can perform batch operations like validation and transformation over sets of files. Another feature of the project is that allows you to share your project settings and transformation scenarios with your coworkers.
The most simple way to organize your XML working files is to place them in a directory on disk, and then to create a corresponding linked folder into the project. If you add new files to that folder, you simply press refresh and the project panel displays the existing files and subdirectories.
If your files are scattered between several folders, but represent the same class of files, you may find useful to join them in a logical folder. For instance having XSLT stylesheet files distributed in several folders, it may be a good idea to add them in the logical folder "XSL".
The operations available on the files and folders in the projects include validation, well-form check and XSLT transformation.
<oXygen/> introduces a new innovative concept called Master Files which simplifies the configuration and development of XML projects. Master Files are the roots of import/include tree of modules. They are defined at project level and are automatically used to determine the context for: validation, editing (content-completion and outliner), refactoring and component search operations. This support is available for XSD, XSL and RNG modules.
When you edit a module after defining the master files, you have the following benefits:
<oXygen/> provides a quick way to locate and open files from the project or from the current DITA Map, based on an index of the project file paths and DITA map references. The new action is available as part of the File menu.
The index can be refreshed on request in order to reflect new additions in the project or in the opened DITA map.
You can specify almost all of the <oXygen/> settings at project level. This makes it possible to pass along with the project XML Catalogs settings, transformation scenarios, formatting options, validation options, editor layout, etc.
Let us take a real world example. You are creating a set of XML Schema files and XSLT stylesheets for editing and publishing a book. You choose to set in the project options the paths to the XML catalogs, the transformation scenarios, the XML formatting settings, the XML parser and XSLT transformer settings. Your colleagues will simply checkout the project from the source repository, and start working immediately. None of them will spend time configuring the editor.
In the next image you can see that the Saxon 6 options are project settings.
Checking the "Project Options" radio button moves the current scenario to the project level: