Re: [api-dev] how to make the macros available to all users of a Windows Terminal server
Jo wrote: 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? I'm not Carsten but I hope I can help too. :-) Basic has an administration file for all of its libraries and just copying libraries won't help without updating this file. Unfortunately this file is part of each user profile so it needs manual operations in all user installations. Not recommended. Deploying libraries for all users admittedly is a little bit awkward in OOo. The best way is to create a UNO package from the libs and install it with unopkg --shared. Creating packages will be supported by the BasicIDE in OOo2.0.3. The created packages of course will work in any OOo2 version. Best regards, Mathias -- Mathias Bauer - OpenOffice.org Application Framework Project Lead Please reply to the list only, [EMAIL PROTECTED] is a spam sink. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [api-dev] how to make the macros available to all users of a Windows Terminal server
Jo wrote: 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-library manifest:full-path=script.xlb/ manifest:file-entry manifest:media-type=application/vnd.sun.star.dialog-library 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? Assumed your Basic library has the name MyBasicLib your package should have the following structure: META-INF/manifest.xml Addons.xcu MyBasicLib/dialog.xlb MyBasicLib/script.xlb and your META-INF/manifest.xml should be: ?xml version=1.0 encoding=UTF-8? !DOCTYPE manifest:manifest PUBLIC -//OpenOffice.org//DTD Manifest 1.0//EN Manifest.dtd manifest:manifest xmlns:manifest=http://openoffice.org/2001/manifest; manifest:file-entry manifest:media-type=application/vnd.sun.star.configuration-data manifest:full-path=Addons.xcu/ manifest:file-entry manifest:media-type=application/vnd.sun.star.basic-library manifest:full-path=MyBasicLib/ /manifest:manifest More information around the package structure can be found in the Developers Guide (http://api.openoffice.org/docs/DevelopersGuide/Components/Components.xhtml#1_9_1_UNO_Package_Installation_Using_unopkg) Juergen - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [api-dev] how to make the macros available to all users of a Windows Terminal server
Jo wrote On 05/23/06 08:29,: 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/[application 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-library manifest:full-path=script.xlb/ manifest:file-entry manifest:media-type=application/vnd.sun.star.dialog-library 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? Hi Jo, Jürgen is right that a package is a better and clean way to deploy changes to the share folder. A package needs a different toolbar definition, so you cannot use the xml file. You can find a description how to create a package toolbar in the OpenOffice.org 2.0 Developer's Guide, chapter 4.7.3 Add-ons. The Developer's Guide can be found here: http://api.openoffice.org/DevelopersGuide/DevelopersGuide.html Regards, Carsten - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [api-dev] how to make the macros available to all users of a Windows Terminal server
Jürgen Schmidt wrote: Jo wrote: Assumed your Basic library has the name MyBasicLib your package should have the following structure: META-INF/manifest.xml Addons.xcu MyBasicLib/dialog.xlb MyBasicLib/script.xlb to make it clear here, Basic libraries are organized in sub folders and MyBasicLib in the package should be the whole folder of the MyBasicLib library including all *.xlb|xba|xdl files. Juergen - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [api-dev] how to make the macros available to all users of a Windows Terminal server
Jürgen Schmidt wrote: Jürgen Schmidt wrote: Jo wrote: Assumed your Basic library has the name MyBasicLib your package should have the following structure: META-INF/manifest.xml Addons.xcu MyBasicLib/dialog.xlb MyBasicLib/script.xlb to make it clear here, Basic libraries are organized in sub folders and MyBasicLib in the package should be the whole folder of the MyBasicLib library including all *.xlb|xba|xdl files. Hi Juergen and Carsten, This is what I get after a fresh installation of OOo (I also removed all the files under Program Files relating to OOo 2.0) E:\C:\Program Files\OpenOffice.org 2.0\program\unopkg.exe add -v --shared etuc.uno.pkg Raising process: file:///C:/Program%20Files/OpenOffice.org%202.0/program/soffice Arguments: -nologo -nodefault -accept=pipe,name=4755ee6b2323560ab4cca595ba99a61a f3624a44c8856e24e8cce3e865173b;urp; Ok. Connecting...Ok. Copie du package : etuc.uno.pkg unopkg done. This is what happens in consecutive runs. (after having done a remove) Copie du package : etuc.uno.pkg unopkg done. That's great but the files are not added to C:\Program Files\OpenOffice.org 2.0\share\basic\ and they don't become available as a module in OOo, so they don't get registered correctly somehow. My manifest file: ?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-library manifest:full-path=ETUC/ /manifest:manifest The directory structure inside the zipped etuc.uno.pkg file: META-INF/manifest.xml ETUC/dialog.xlb ETUC/ETUC.xba ETUC/script.xlb I'm not trying to add the toolbar for the moment, so I suppose I don't need to add an addons.xcu file. I'm trying to keep it simple. I see that a temp folder is created at C:\Program Files\OpenOffice.org 2.0\share\uno_packages\cache\uno_packages\340A.tmp_\etuc.uno.pkg\etuc.uno\META-INF\manifest.xml and all the packaged files are in there, but they are not added to C:\Program Files\OpenOffice.org 2.0\share\basic\ I had expected to see an ETUC folder appear there. And they are not registered as a library in OOo either. Nothing shows up there. This is getting over my head. I hope you can help me out. Cheers, Jo - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [api-dev] how to make the macros available to all users of a Windows Terminal server
Hi and all the packaged files are in there, but they are not added to C:\Program Files\OpenOffice.org 2.0\share\basic\ I had expected to see an ETUC folder appear there. will be in C:\Program Files\OpenOffice.org 2.0\share\uno_packages subdirectory And they are not registered as a library in OOo either. Nothing shows up there. that is strange .. did you close OOo (quickstarter too) Laurent -- Laurent Godard [EMAIL PROTECTED] - Ingénierie OpenOffice.org Indesko http://www.indesko.com Nuxeo CPS http://www.nuxeo.com - http://www.cps-project.org Livre Programmation OpenOffice.org, Eyrolles 2004 - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [api-dev] how to make the macros available to all users of a Windows Terminal server
Jo wrote: Jürgen Schmidt wrote: Jürgen Schmidt wrote: Jo wrote: Assumed your Basic library has the name MyBasicLib your package should have the following structure: META-INF/manifest.xml Addons.xcu MyBasicLib/dialog.xlb MyBasicLib/script.xlb to make it clear here, Basic libraries are organized in sub folders and MyBasicLib in the package should be the whole folder of the MyBasicLib library including all *.xlb|xba|xdl files. Hi Juergen and Carsten, This is what I get after a fresh installation of OOo (I also removed all the files under Program Files relating to OOo 2.0) E:\C:\Program Files\OpenOffice.org 2.0\program\unopkg.exe add -v --shared etuc.uno.pkg Raising process: file:///C:/Program%20Files/OpenOffice.org%202.0/program/soffice Arguments: -nologo -nodefault -accept=pipe,name=4755ee6b2323560ab4cca595ba99a61a f3624a44c8856e24e8cce3e865173b;urp; Ok. Connecting...Ok. Copie du package : etuc.uno.pkg unopkg done. This is what happens in consecutive runs. (after having done a remove) Copie du package : etuc.uno.pkg unopkg done. That's great but the files are not added to C:\Program Files\OpenOffice.org 2.0\share\basic\ and they don't become available as a module in OOo, so they don't get registered correctly somehow. My manifest file: ?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-library manifest:full-path=ETUC/ /manifest:manifest The directory structure inside the zipped etuc.uno.pkg file: META-INF/manifest.xml ETUC/dialog.xlb ETUC/ETUC.xba ETUC/script.xlb I'm not trying to add the toolbar for the moment, so I suppose I don't need to add an addons.xcu file. I'm trying to keep it simple. I see that a temp folder is created at C:\Program Files\OpenOffice.org 2.0\share\uno_packages\cache\uno_packages\340A.tmp_\etuc.uno.pkg\etuc.uno\META-INF\manifest.xml and all the packaged files are in there, but they are not added to C:\Program Files\OpenOffice.org 2.0\share\basic\ I had expected to see an ETUC folder appear there. no there will be no folder under share\basic. Shared packages are maintained under share \uno\packages. And they are not registered as a library in OOo either. Nothing shows up there. I have test it with a package containing a Basic library and it works as expected, even when i deploy in a running office. You can send me your package for verifying if you want. Juergen - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [api-dev] how to make the macros available to all users of a Windows Terminal server
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/[application 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? Jo - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [api-dev] how to make the macros available to all users of a Windows Terminal server
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/[application 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. Juergen Jo - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
