Kay Ramme - Sun Germany - Hamburg schrieb:
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?
Yes, but this is ok for the first shot - with this mapping I try to
learn much more
about the whole system. Perhaps the second attempt can be richer then ...
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?
Yes, this sound like old technology, but I want to have a system, which
"knows",
what all these interfaces can do - which is not the case in the BASIC
IDE and its
much easier for me - due to Smalltalk interactive system - to test and
play with
the system ... and I can browser through all classes.
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've read about Binary UNO - but the latest documents I've found where
dated around 2001
and I thought, that this interface had been cancelled - in favour of C++.
Thanks for your answer.
Marten
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
