Adrian Buza wrote:   Thanks, Adrian.

If you want to relocate the frameworks directory to a different location, go to Options > Preferences, Global, enable the option "Use a custom frameworks directory" and browse for the new directory.  Note that if you still want to use some of the built-in frameworks that Oxygen provides you will have to manually copy them to this new directory from the original frameworks directory(Oxygen/frameworks).

  The problem with that approach is every time I upgrade oXygen.  In that case, I'd like 1/ the built-in framework to be upgraded (or replaced if you prefer) and 2/ the framework I create or install from third-parties to be kept...  I guess that could be easily solved by having an "additional framework dir" (as opposed to "another location for the framework dir").   Thanks for the explanation!  Regards, --  Florent Georges http://fgeorges.org/ http://h2oconsulting.be/

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/

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/

Hi Florent, Just to clarify this: On 2/22/12 6:00 PM, Florent Georges wrote:

...

${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 am not sure to understand this paragraph.

Let's say you have a framework that is stored in [oXygen]/frameworks/xproject/xproject.framework Then, Adrian proposed that the ${currentFramework} will be expanded to the folder containing your framework, in this case that will be [oXygen]/frameworks/xproject Thus, basically you should be able to use this variable to specify paths to resources needed for the framework configuration (of course, this will be equivalent with allowing relative locations that will be automatically expanded taken into account the .framework configuration file that contains them. Best Regards, George -- George Cristian Bina <oXygen/> XML Editor, Schema Editor and XSLT Editor/Debugger http://www.oxygenxml.com