Hi,
Peter Eberlein wrote:
I'm prepairing the 2.0 installation right now with a default-userprofile.
You shouldn't need to place xcu files into the user profile. Such files
can be installed in $install/share and then serve as defaults for all
users. With some manual editing you can even mark some of the defaults
as final (i.e. the user can't override them).
The simplest way to do this is to install the xcu files with unopkg:
- give the xcu files a unique name
- run 'unopkg add --shared MySettings.xcu'
There are other (more complicated) ways, if you can't have the files
managed by unopkg.
If the config-file could be placed in the userprofile, I would create it
now and deploy it with 2.0. After updating to 2.0.1, no changes in the
userprofile would be necessary (it's a little bit cumbersomely, because
every user has its own directory on the server).
If you use the 'share' way, you can update defaults at any time later.
If you place the new configfile there now, it won't have any effect. As
the corresponding schema (xcs) file isn't there, the office won't even
look at it. When the schema (and the code that attempts to use the data)
is installed by an update, then the file would automatically take effect.
For security reasons it is better to have it in the shared folder,
because the user has no write access there.
Yep.
Jörg
--
Joerg Barfurth Sun Microsystems - Desktop - Hamburg
>>>>>>>>>>>>>>>>>> using std::disclaimer <<<<<<<<<<<<<<<<<<<<<<<
Software Engineer [EMAIL PROTECTED]
OpenOffice.org Configuration http://util.openoffice.org
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
