Let me clarify with an example. ${frameworksDir} expands to the frameworks directory. By default that is: /path/to/oxygen/frameworks If you use a custom frameworks directory, then ${frameworksDir} points to that directory. The DocBook 4 framework file is now located in: /path/to/oxygen/frameworks/docbook/docbook4.framework Currently the references to any files from the DocBook 4 framework directory are like this: ${frameworksDir}/docbook/path/to/file These references are generally made from inside the framework file itself. ${framework(docbook)} would also work, but it still specifies the name of the framework subdir and we would like to avoid that as well. What we are planning is to use a generic editor variable ${currentFramework}(or ${framework}) that expands to the parent directory of the .framework file. So, for the DocBook 4 example above that would translate to : ${currentFramework} when used in the DocBook 4 framework context would expand to: /path/to/oxygen/frameworks/docbook So the references would be: ${currentFramework}/path/to/file This eliminates both the dependence on the common frameworks dir and the specific framework subdir will also resolves the problems that appear when you want to duplicate a framework. I've added your suggestion to the issue and we will also consider that possibility. Regards, Adrian Adrian Buza oXygen XML Editor and Author Support Florent Georges wrote:
Adrian Buza wrote
Thanks, Adrian.
There are a few possible solutions, one being to replace the references to ${frameworksDir}\<frameworkName> with a new editor variable. e.g. ${currentFramework}. This is still open for debate.
That would impose one to know where the framework is installed (either in the "main" or "additional" framework dir), which IMHO would make the feature less useful. What about something like that:
${framework(xspec)}
It would look for a subdir "xspec" in either framework dir, with one taking precedence over the other (not 100% sure which one should have precedence though).
Regards,
-- Florent Georges http://fgeorges.org/ http://h2oconsulting.be/