Hi,
Well, not being a Python-savvy person at all, it seems that pyUNO needs
to be adapted to each new version of OOo to support its new classes? If
so, this will be an ongoing run-up to match both with each other?
only when the component model UNO itself is extended or changes, pyuno
needs to be adopted. Pyuno creates types on the fly out of ooo's type
library.
As OOo has a Java based scripting framework in place it would be
possible to use Jython as a scripting language for executing Python
scripts. Using Apache's BSF, which has a Jython engine, the interaction
between OOo and Jython should be rather easyly implementable with the
scripting framework (use the ooRexx scripting framework code employing
BSF to dispatch the ooRexx scripts and change a few lines). Maybe this
would alleviate the need to constantly run-up to the latest OOo release
and instead make it possible to have a "stabler" support for Python?
Again, I am not a "Python-person", so I do not know whether the Jython
implementation would be acceptable at all.
you are welcome to try and compete with the existing implemtation ...
Bye,
Joerg
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
