There has been some discussion about updating the PyUNO engine, there are some changes on 3.x branch and some advantages as well. This is not only the pyuno bridge but the way python works now.
Since the original developer has wonder off the project, is up to the community to support it. There has been some technical discussions not long ago on the dev@ mailing list about this move. I would suggest to reffer to it and maybe revive it somehow. About technical documentation, I would start with the code itself, although developed on C++ looking at it might help understand how the bridge works. On 12/18/12, Kázmér Koleszár <[email protected]> wrote: > Hi All, > > We at Multiracio are developing extensions mostly in Python, and so work a > lot with PyUno, and have some troubles with it. We would like to put more > efforts in fixing bugs and developing PyUno in the future and make it more > stable and reliable, but we would need some more technical information, > some kind of design document, as the structure seems sometimes quite > obscure... Can you help us in that ? > > Thanks, > Kazmer Koleszar > Multiracio, Hungary > -- Alexandro Colorado PPMC Apache OpenOffice http://es.openoffice.org
