Hi Marten,
Marten Feldtmann wrote:
Actually I'm starting a wrapper for VisualAge Smalltalk for OpenOffice.
Good thing.
To get into this area, I started to write the interface from Smalltalk
to OLE/COM (.NET is not a solution) and more or less the principle works.
This is obviously windows only, isn't it?
I wrote a code generator, which creates wrapper classes and though I'm
still in the early phase it seems to be good for working. Of course one
may get lots of classes (actually I have now around 1500 new classes only
for OpenOffice).
You are generating code for OOos UNO API? Isn't Smalltalk supporting
reflection etc. so that you code avoid this?
Due to the fact, that I would like to have access from VA Smalltalk to
OpenOffice from Linux, Windows, OS/2 and Solaris I need a different
low level access to the OpenOffice system.
So, COM is not your friend here. You can either access UNO via C (Binary
UNO) or C++ (C++ UNO) or via network connections (Remote UNO).
I do not want to create new components written in Smalltalk - just program
OpenOffice from Smalltalk programs.
If you have access to UNO objects in Smalltalk, there is actually not
much missing to also be able to implement components.
I also would not like to use C++. The best solution is access via plain C
code ... is this possible ? Which documents do I have to investigate
further
on to get a first success.
This is possible, this is called Binary UNO. Please look around on the
udk.openoffice.org pages and on the api.openoffice.org pages. The module
implementing Binary UNO is cppu.
Thanks for any information - there's lots of documentation out there,
but it
does seem to be difficult to get the correct one.
Just let me know if you need assistance ....
Marten
Kay
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
