Adrian Buza wrote: Hi, Thanks Adrian, and sorry for the late response.
${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.
So if I am right, the built-in frameworks won't be part of oXygen anymore when we use a custom frameworks dir, so they won't be updated when updating oXygen itself. Unless I missed something. This is not really a viable solution I think.
${frameworksDir}/docbook/path/to/file These references are generally made from inside the framework file itself.
Sounds weird to me. Why not using relative references in files from within the framework itself? I thought more about references in scenarios.
${framework(docbook)} would also work, but it still specifies the name of the framework subdir and we would like to avoid that as well.
But you need it with either techniques, don't you? Whether you say ${framework(docbook)} or ${frameworksDir}/docbook, you explicitely use the name of the framework.
${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. BTW, I like Chris's idea of a framework path ;-) Regards, -- Florent Georges http://fgeorges.org/ http://h2oconsulting.be/