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 the only way to get mergeable lists of strings. That statement I can't agree with. The configuration registry is basically a database. It is not uncommon in database design to use arbitrary key names. But the name is never used as the value, because the two are semantically different. Similarly, in the OpenOffice.org registry, arbitrary key names would be used where required, with the key value used as the configuration settings. To get a mergeable list of strings, the key values would be merged, not the key names. > Instead you need to know a list of unspecified key names. You don't > suggest to hardcode "com.acme.supertemplate" into OOo, do you? I'm not suggesting this. The key names would identify the source of each path setting, but to OOo, the names would be irrelevant and it would not need to know them. OOo would enumerate all of the keys under org.openoffice.Office.Paths/<pathname>/InternalPaths, just like it does now, except it would concatenate the key values into a path list, instead of concatenating the key names. 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. Comments are welcome. The instructions are located at: http://openofficetechnology.com/node/50 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 Thank you, Allen --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
