Python/UNO/OpenOffice?
kenneth.m...@sbcglobal.net
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
gregarican
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...
Gary Herron
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.
Gary Herron
gregarican
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.
Sybren Stuvel
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 ;-)
Sybren
--
Sybren Stüvel
Stüvel IT - http://www.stuvel.eu/
wesley chun
(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.
cheers,
-- wesley
- - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
"Core Python Programming", Prentice Hall, (c)2007,2001
http://corepython.com
wesley.j.chun :: wescpy-at-gmail.com
python training and technical consulting
cyberweb.consulting : silicon valley, ca
http://cyberwebconsulting.com
John Machin
> kenneth.m...@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:
| C:\Program Files\OpenOffice.org
2.0\program\python-core-2.3.4\bin>python
# 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)?
Cheers,
John
Sybren Stuvel
> 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.
That's not nice.
> Has anyone managed to get further than this on Windows (XP Pro, SP
> 2)?
Not me - I'm not using Windows. If anyone knows more about this,
please post here or post a comment at
http://www.stuvel.eu/archive/31/article-about-openofficeorg-and-python
so that I can improve the article.
olive
Is there any OO compiled with P2.4x for Windows somewhere ?
Colin J. Williams
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 W.
John Machin
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?
TIA,
John
olive
Here is something that works for me under XPsp2 to either save a doc or
save it as PDF:
filepath = argv[0]
exportpdf = argv[1]
ctxLocal = uno.getComponentContext()
smgrLocal = ctxLocal.ServiceManager
resolver =
smgrLocal.createInstanceWithContext("com.sun.star.bridge.UnoUrlResolver",ctxLocal)
url =
"uno:socket,host=localhost,port=2002;urp;StarOffice.ComponentContext"
ctx = resolver.resolve(url)
smgr = ctx.ServiceManager
desktop =
smgr.createInstanceWithContext("com.sun.star.frame.Desktop",ctx)
properties = []
if exportpdf == "yes":
p = PropertyValue()
p.Name = "Hidden"
p.Value = True
properties.append(p)
properties = tuple(properties)
doc = desktop.loadComponentFromURL("file:///c:"+filepath+".odt" ,
"_blank", 0, properties)
if exportpdf == "yes":
properties = []
p = PropertyValue()
p.Name = "Overwrite"
p.Value = True
properties.append(p)
p = PropertyValue()
p.Name = "FilterName"
p.Value = 'writer_pdf_Export'
properties.append(p)
properties = tuple(properties)
doc.storeToURL("file:///c:"+filepath+".pdf", properties)
else:
doc.store()
doc.dispose()
You must start OO this way first:
cd C:\Program Files\OpenOffice.org 2.0\program
soffice "-accept=socket,host=localhost,port=2002;urp;"
olive
... and you have to start your py file with:
import uno, sys, socket
from com.sun.star.beans import PropertyValue
... and your start_oo_server.bat file with:
@SET PYTHONPATH=C:\Program Files\OpenOffice.org 2.0\program;C:\Program
Files\OpenOffice.org 2.0\program\python-core-2.3.4\lib
@SET PATH=C:\Program Files\OpenOffice.org 2.0\program;C:\Program
Files\OpenOffice.org 2.0\program\python-core-2.3.4\bin
John Machin
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
Sybren Stuvel
> open an XLS ffile, and it worked!
> I'll try to see why that worked and my previous experiment crashed
> inside a DLL.
Thanks, keep us posted!