Are then any currently active and reasonably mature Python plugins/ apis/whatever for programming/scripting OpenOffice? The page I've found is http://udk.openoffice.org/python/python-bridge.html, but it was last updated more than a year ago.
Just because the last code update was a little over a year ago doesn't mean the UNO project is dead. If the OpenOffice API has remained basically the same since UNO was last updated and the Python wrappers are relatively comprehensive then it should fit the bill. Googling around the UNO project was the only thing I found off-hand as well...
kenneth.m.mcdon...@sbcglobal.net wrote: > Are then any currently active and reasonably mature Python plugins/ > apis/whatever for programming/scripting OpenOffice? The page I've > found is http://udk.openoffice.org/python/python-bridge.html, but > it was last updated more than a year ago.
kenneth.m.mcdon...@sbcglobal.net wrote: > Are then any currently active and reasonably mature Python plugins/ > apis/whatever for programming/scripting OpenOffice? The page I've > found is http://udk.openoffice.org/python/python-bridge.html, but > it was last updated more than a year ago.
> Thanks, > Ken
I don't believe that information is out-of-date. I use the python-bridge with the OpenOffice version 2.0.3 quite successfully. In my case I open a spread sheet and search around for and extract various values. It works just fine for me.
That's what I would imagine. Kind of like calling some Microsoft Office COM/OLE methods in a wrapper. As long as the wrapper has most of the methods you need and the core COM/OLE calls don't change then that's a great start.
Gary Herron wrote: > kenneth.m.mcdon...@sbcglobal.net wrote: > > Are then any currently active and reasonably mature Python plugins/ > > apis/whatever for programming/scripting OpenOffice? The page I've > > found is http://udk.openoffice.org/python/python-bridge.html, but > > it was last updated more than a year ago.
> > Thanks, > > Ken
> I don't believe that information is out-of-date. I use the python-bridge > with the OpenOffice version 2.0.3 quite successfully. In my case I open > a spread sheet and search around for and extract various values. It > works just fine for me.
kenneth.m.mcdon...@sbcglobal.net enlightened us with:
> Are then any currently active and reasonably mature Python plugins/ > apis/whatever for programming/scripting OpenOffice? The page I've > found is http://udk.openoffice.org/python/python-bridge.html, but it > was last updated more than a year ago.
Aside from what has already been said, it might be nice for you to read my article about OOo and Python at http://www.stuvel.eu/ooo-python ;-)
as others have said, that project provides a working interface to OOo (OpenOffice 2 on Ubuntu Breezy and Dapper). i've made several posts to this regard over the summer here on CLP. i was mostly using it to "mess around" with documents in StarWriter.
Sybren Stuvel wrote: > kenneth.m.mcdon...@sbcglobal.net enlightened us with: > > Are then any currently active and reasonably mature Python plugins/ > > apis/whatever for programming/scripting OpenOffice? The page I've > > found is http://udk.openoffice.org/python/python-bridge.html, but it > > was last updated more than a year ago.
> Aside from what has already been said, it might be nice for you to > read my article about OOo and Python at > http://www.stuvel.eu/ooo-python ;-)
Hi, Sybren. I tried folloing your recipe on Windows with OOo 2.0 ...
Minor problem: the executable is called soffice, not ooffice.
Major problem: it crashed right at the start, somewhere in the maze of dlls.
The following interactive session reproduces the problem:
# OOo includes a complete python distribution. Note the directory name says 2.3.4 ...
| Python 2.3.5 (#62, Feb 8 2005, 16:23:02) [MSC v.1200 32 bit (Intel)] on win32
... but the program identifies itself as 2.3.5
| Type "help", "copyright", "credits" or "license" for more information. | >>> import sys | >>> sys.path.append(r'C:\Program Files\OpenOffice.org 2.0\program')
# The above directory contains all the dlls plus a handful of python files
| >>> import pyuno # from pyuno.dll; there's no other pyuno.* | >>> _g_ctx = pyuno.getComponentContext()
# crash
Has anyone managed to get further than this on Windows (XP Pro, SP 2)?
Sybren Stuvel wrote: > Aside from what has already been said, it might be nice for you to > read my article about OOo and Python at > http://www.stuvel.eu/ooo-python ;-)
wesley chun wrote: > as others have said, that project provides a working interface to OOo > (OpenOffice 2 on Ubuntu Breezy and Dapper). i've made several posts > to this regard over the summer here on CLP. i was mostly using it to > "mess around" with documents in StarWriter.
> wesley.j.chun :: wescpy-at-gmail.com > python training and technical consulting > cyberweb.consulting : silicon valley, ca > http://cyberwebconsulting.com
I've done some small things with Python/OpenOffice, using Windows XP. They appear to work OK.
It seems that there is only one person to maintain the Python interface and that there few users - no critical mass. I hope that this will change as OpenOffice is, with the exception of the Base component, a solid package. The base (database) component is evolving.
Colin J. Williams wrote: > I've done some small things with Python/OpenOffice, using Windows XP. > They appear to work OK.
As you might have noticed from my earlier post, I can't get off the ground. Can you please give an example (with code) of a "small thing" that works OK?
Many thanks for all that, olive; I made the minimal hacks to make it open an XLS ffile, and it worked! I'll try to see why that worked and my previous experiment crashed inside a DLL. Cheers, John
> Many thanks for all that, olive; I made the minimal hacks to make it > open an XLS ffile, and it worked! > I'll try to see why that worked and my previous experiment crashed > inside a DLL.