Re: [udk-dev] UNO python and openoffice. ManualHowto
On Thu, 21 Aug 2008 08:26:53 -0500, Juergen Schmidt [EMAIL PROTECTED] wrote: Hello, I created a little manual on how to use openoffice, with python and uno. Maybe we could document the already existant code that we have out there. I dunno why but i didnt notice that there are some interesting scripts writen in python on the python uno page. http://udk.openoffice.org/python/python-bridge.html ooextract.py A command line tool, that extracts the text, html or pdf content from a StarWriter document and writes it to a different file or (optionally) prints it to stdout (grep your office documents). oomerge.py A command line tool, that creates a new document by appending multiple single documents swriter.py A command line program, that fills a writer document with some text and tables. swritercomp.py, swritercompclient.py Same as above, but implemented as a python UNO component, so that it runs within the office process. This shows the performance benefit of having scripts run within one process. You must add the swritercomp.py program with the pkgchk tool (see below) to the office installation and can then use the swritercomp_client.py program to execute it. biblioaccess.py A command line program, that displays the contents of the biblio sample database that comes with OpenOffice.org. python-tokencounter-calc-addin.oxt Adds a function named tokencount to calc, which counts the number of words within a calc cell. After adding the extension, the office must be restarted (including terminating the quickstarter) to make the function appear in the function list. Your example (Please send more examples, so that they can be added here). -- Alexandro Colorado CoLeader of OpenOffice.org ES http://es.openoffice.org - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[udk-dev] Re: My first Calc addin: problem with exception handling
Andrea wrote: I have read that one should use the same compiler used to compile OO. Is it (still) true? maybe. I don't know. Is this my problem? No. I managed to find what was the problem: I followed this example http://wiki.services.openoffice.org/wiki/SimpleCalcAddIn but I think it is not using the correct options for the linker. I have found a different set of options in the example directory of the sdk. Now I can raise exceptions. In particular this one seems to be important -Wl,--version-script,../component.uno.map What is the definitive guide to options to compile a Calc add-in? Andrea - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [udk-dev] Re: My first Calc addin: problem with exception handling
Andrea wrote: Andrea wrote: I have read that one should use the same compiler used to compile OO. Is it (still) true? maybe. I don't know. it is recommended to avoid problems Is this my problem? No. I managed to find what was the problem: I followed this example http://wiki.services.openoffice.org/wiki/SimpleCalcAddIn but I think it is not using the correct options for the linker. I have found a different set of options in the example directory of the sdk. Now I can raise exceptions. In particular this one seems to be important -Wl,--version-script,../component.uno.map What is the definitive guide to options to compile a Calc add-in? that is a good question. The options used in the SDK should be ok but i have to confess that it is not well documented and not really well arranged. It's of course not easy to maintain the set of necessary options because i want to limit them on the necessary minimum in the SDK env. Anyway i have it on a longer todo list to clean up this in the SDK. Maybe i should create a new wiki page where i document the options and maintain it. The problem with the wiki is that docu can be easy created but can be also become out dated fast and it's often not maintained. Juergen Andrea - 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]
