Allen Pulsifer schrieb:
Hello Joerg,
Thank you for your response. Just to respond further:
The Current/Default distinction in that place was misguided.
That should really be achieved via layering.
I agree with this.
There are other places in OOo where dynamically created keys have such
s
> > I also submitted two bug reports.
> >
> > http://qa.openoffice.org/issues/show_bug.cgi?id=70688
> > http://qa.openoffice.org/issues/show_bug.cgi?id=70687
>
> Thanks Allen, the developer responsible for this is currently
> on vacation but he surely will have a look when he is back
> end
> But you've hit the nail on the top. We have prepared for two
> ways of working with pathes: "UserPaths" can be overwritten
> like described here, "InternalPaths" are mergeable. So an
> admin that wants to write his own path as described by Allen
> and doesn't want to allow for changes made by
Allen Pulsifer wrote:
> I tested the operation of path configuration in OOo v2.0.4 and wrote up
> instructions on how it can be configured by an administrator. Note these
> instructions are based on how the path settings have been tested to work,
> not how they are intended or documented to work.
Joerg Barfurth wrote:
>> If an administrator wanted to override the value of
>> Template path used by the application, he/she could do so with a short
>> fragment of XML that simply replaces the value of
>> org.openoffice.Office.Paths/Template/InternalPaths/org.openoffice.app.
>
> Apparently it
Hello Joerg,
Thank you for your response. Just to respond further:
> The Current/Default distinction in that place was misguided.
> That should really be achieved via layering.
I agree with this.
> There are other places in OOo where dynamically created keys have such
> significance. This is
Allen Pulsifer schrieb:
I'm looking over the new Path's configuration and it seems to me the
implementation is awkward and does not follow the usually configuration
paradigm.
In OpenOffice.org v2.0.3 and prior, paths were configured via
org.openoffice.Office.Common/Path/Default and
org.openof
I'm looking over the new Path's configuration and it seems to me the
implementation is awkward and does not follow the usually configuration
paradigm.
In OpenOffice.org v2.0.3 and prior, paths were configured via
org.openoffice.Office.Common/Path/Default and
org.openoffice.Office.Common/Path/Curre
