Kay Ramme - Sun Germany - Hamburg wrote: [...]
Anyway, even using the mentioned registry entry does not seem to achieve what you want to achieve, as this registry entry is globally unique and does not belong to the office installation. So, what you actually want, is an OOo installation specific entry, which points to the to be used URE.
No, not necessarily. (If OOo-wo-URE wants to store a pointer to its underlying URE, it need not use the registry at all.) Let me rephrase my thoughts:
There are three steps involved. First, when OOo-wo-URE is installed, it needs an installed URE, so that needs to be found somehow (and HKEY_CLASSES_ROOT\Software\OpenOffice.org\URE pointing at "the machine's default URE" might come in handy here). Second, OOo-wo-URE needs to have this information (i.e., the location of its underlying URE) available at runtime. And third, it should be easy for the user to change that information, to at least be able to (a) at installation time combine the OOo-wo-URE with an arbitrary URE (not necessarily "the machine's default URE"), and (b) later on move around the installation locations of the OOo-wo-URE or its underlying URE, or both.
AFAIK, the right place for a URE_BOOTSTRAP deployment variable is an OOo installation specific registry entry, and, as you already suggested, to introduce .ini files for all executables, so the latter may be avoided by seamless integration/support of windows registry entries into the deployment parameter approach.
Not sure about OOo storing its deployment data in the registry. What would the keys look like? What about having two instances of OOo installed that are "sufficiently similar" from a code-base point of view (i.e., would probably both use the same keys), but nevertheless shall have different deployment data?
-Stephan [...] --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
