Hi,
the most important thing is the UNO API from OOo. UNO the underlying component model will be extracted from OOo soon so that it should be possible for other applications to use it as well.
The whole API is defined in IDL and OOo provides "one" possible implementation for this abstract API. So if other applications want to be able to run OOo macros they can provide an implementation for this API too. Furthermore they have to provide a BASIC runtime. Probably there is much more to do but without the mentioned things you won't be able to run macros either way.
And of course the best thing would be to implement the API from scratch because otherwise you have to reuse more or less the whole OOo ;-)
Juergen
M. Fioretti wrote:
Greetings,
OpenDocument can be used by any Office suite or other software, but what if a file also contains OO.o macros?
What if developers of KOffice, AbiWord, whatever... wanted to add this
support to their program?
Is it possible? How? How much big of a task would it be? Which kind of work should be done? Which part of the OO.o codebase should be imported? Is it possible license wise, to use it into a GPL program? Or should it be implemented from scratch? If so, where are the specs?
Which other technologies does it depend on? Java, anything else?
In general, what is the relevant documentation to read, for a developer? And the proper mailing list where to ask further questions?
Any comment is appreciated.
Ciao, Marco
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
