Kay Ramme - Sun Germany - Hamburg wrote:
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.
My understanding of windows registry entries is, that they actually
serve (or at least partly do so) the same purpose as the deployment
parameters. In the sense, that if a user wants to change the URE to be
used by a particular office installation, he/she would change a registry
entry of that installation for that reason.
and
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?
You certainly would need different registry entries for different
installations, while having one global entry pointing to the "default"
installation.
Again: If I have two instances A and B of an application installed, and
want to have a per-installation deployment variable C for that
application stored in the registry, what would the involved registry
keys have to look like for instance A to have C with value D and
instance B to have C with value E?
-Stephan
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
