Jürgen Schmidt wrote:
> Jo wrote:
>> Carsten Driesner - Sun Germany - ham02 - Hamburg -
Software Engineer
>> wrote:
>>> Jo wrote On 05/22/06 10:43,:
>>>> Hi,
>>>>
>>>> I created a toolbar, but when I log off and
on as a different user.
>>>> I can't find my toolbar. How can I deploy
a toolbar to different
>>>> users?
>>>
>>> Hi Jo,
>>>
>>> If you create a custom toolbar it's your
personal toolbar. You have
>>> to manually copy it from your user folder to
the Office share
>>> folder. The location of your user folder
depends on your system.
>>> Windows 2000/XP=<Windows
installation>/Documents and
>>> Setttings/<Username>/Application
Data/OpenOffice.org2
>>> Unix:<User home>/.openofficer.org2
>>>
>>> A custom toolbar is currently always associated
to a module. It
>>> depends on the module you used to create your
toolbar, where you can
>>> find your toolbar.
>>> Below the user folder you can find the user
interface configuration
>>> folders, splitted into application modules.
>>> <User
folder>/user/config/soffice.cfg/modules/[application
>>> module]/toolbar. There you should find your new
toolbar with a name
>>> like custom_toolbar[n]. This file must be
copied into the share
>>> folder of your Office installation, which has
the same folder hierachy.
>>> <Office
installation>/share/config/soffice.cfg/modules/[applicati
on
>>> module]/toolbar.
>>>
>>
>> Hi Carsten,
>>
>> Many thanks for your answer. The next problem is
that when logged on
>> as a different user the library containing the
macros is not
>> available. I tried to also copy the basic code as
follows:
>>
>> C:\Documents and Settings\My
Username\Application
>> Data\OpenOffice.org2\user\basic\ETUC\*.*
>> to C:\Program Files\OpenOffice.org
2.0\share\basic\ETUC\
>>
>>
>> But the module is not recognized any more. When I
try to do it
>> properly, then the Add... button becomes grey when
I select Macros
>> and Dialog boxes of OpenOffice.org.
>>
>> Can you help me out on this one too?
>
> You should create a UNO package containing your Basic
library and the
> toolbar configuration. This package can be deployed as
a shared
> package (administrator rights are necessary) to provide
access for all
> users of this office installation.
>
> You shouldn't copy or modify anything directly, use
the clean way by
> using a package. This has the advantage hat you can
remove the whole
> package in clean way as well.
>
Hi Juergen,
I've spending all evening yesterday to find out how such a
package needs
to be set up. Do you have a url where I can find
straightforward
instructions? What file goes where. What do I put in the
manifest file?
Now I have this:
<?xml version="1.0"
encoding="UTF-8"?>
<!DOCTYPE manifest:manifest PUBLIC
"-//OpenOffice.org//DTD Manifest
1.0//EN" "Manifest.dtd">
<manifest:manifest>
<manifest:file-entry
manifest:media-type="application/vnd.sun.star.basic-li
brary"
manifest:full-path="script.xlb"/>
<manifest:file-entry
manifest:media-type="application/vnd.sun.star.dialog-l
ibrary"
manifest:full-path="dialog.xlb"/>
</manifest:manifest>
Is a reference to the .xba file also needed? Or does it find
that in the
script.xlb file? How can I incorporate the information about
the toolbar?
Many thanks,
Jo
------------------------------------------------------------
---------
To unsubscribe, e-mail: dev-unsubscribe api.openoffice.org
For additional commands, e-mail: dev-helpapi.openoffice.org
|