[oXygen-user] Document type & framework: external storage
Adrian Buza
adrian at sync.ro
Wed Feb 15 03:27:54 CST 2012
Hi,
I see your point. However, implementing an "additional framework dir"
isn't that simple right now. All the frameworks depend on an editor
variable that points to the frameworks directory: ${frameworksDir}. This
assumes the frameworks directory is unique.
${frameworksDir} would have to be resolved to a different location when
the framework is located in the "additional framework dir" instead of
the default framework directory. This complicates things to some degree.
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.
I've logged your suggestion on our issue tracking tool.
Regards,
Adrian
Adrian Buza
oXygen XML Editor and Author Support
Florent Georges wrote:
> 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/
>
>
More information about the oXygen-user
mailing list