-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Hi George, I'm checking out 14 beta and like all the new features. I'm having trouble understanding how Master Files should work, however. I've enabled Master Files for a project that contains DocBook docs that use xinclude and added the two "book" files. I see that I can validate or transform all the master files at once or individual master files, but don't see any other changes. For example, the outline view is the same when I'm editing a file included by one of the master files (I gather that's what a "module" is). When I validate a module, it does not appear to validate the master (e.g. if I put an xref in the module with a linkend value that would be valid only in the context of the master, it's marked as invalid). Am I misunderstanding how Master Files should work? Thanks, David On 05/18/2012 08:53 AM, George Cristian Bina wrote: ...
*Master files* In version 14 oXygen introduces a new innovative concept called "Master files" which simplifies the configuration and development of XML projects. The Master Files are defined at project level and are automatically used by oXygen to determine the context for operations such as validation, content-completion, refactoring or search for XSD, XSL and RNG modules. A "Master" file generally means the root of an import/include tree of modules. * Benefits: - When a module is validated oXygen will automatically identify the master files which include that module and it validates all of them, thus the module will be validated in the context it is used from. You will see from this how a change in that module affects your whole project. - When you edit a module the Outline view and the content completion will present all the components collected starting from the Master files which include that module, thus you get to see all the referable components even if they are defined in the main file or in other modules. - Search and refactoring actions, like search references or rename components operate by default on the scope defined by the Master Files * How to define the Master Files: - Drop files in the "Master Files" logical folder in the project - Use the "Add to Master Files" contextual menu action on a file that you want to mark as Master file - Use the "Add Files" contextual menu action available on the "Master File" logical folder * Best practices defining Master Files: - Add only the top level files, the ones which are the roots of the include/import graph - Keep the file set to a minimum. Do not add standalone files (the ones which do not import or include other files). Adding too many files may affect performance
-----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.11 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/ iQEcBAEBAgAGBQJPvP5XAAoJEMHeSXG7afUhC+0IAIoo0jVNTvR8u086CaV8HJxf etKK+4CDGrgqDkKOwUhEuI9X6Mk12MDDTpHmsCaq5/xaQTzSrTw0PVq4EyYRkxrp 3hsNVPsHQTinQx+2FaD9QaB8wRIBHcVHnmN4rYegN4nsvoe6LwBqcMM5ybOjvzNX ul/iXFIhwbaVpLB6B5gabHJXIKaFeN8bmgv6NgI1T0ykjRnnnVVBKvF47iLRgkWz erW36CXaYtoHeIR5GJpugWO3FkaqLJVFdtA06VYcyo6hKE9NHuu8PBdTqkENEwAB VUWGjQDRlljpfxUYn8h0cR0B+uG6ZL2yDCdaYvDz2U/fgvzvLE3zyqe9OEncm+k= =DoMI -----END PGP SIGNATURE-----