Quoting "M. Fioretti" <[EMAIL PROTECTED]>:

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

--
Marco Fioretti                    mfioretti, at the server mclink.it
Fedora Core 3 for low memory      http://www.rule-project.org/


Interesting point and I think is an issue regarding each office manufacturer to
support the macros model since is NOT agnostic to the document but to the
actual suite.


From a programming point of view is not obvious that it would be supported since
there might be OS (Office Suite) exclusive. As for the document this CAN be
modified but it will also represent a channel.


Everytime I think on OpenDocument I like to compare it with e-mails,
unfortunately there are no extensions on emails and most of the extensions are
for the client (weather report, mail minder etc).

My take is that the challenge exceed our scope and a common document-base macros
could be done on a way that work externally (similar to the Ruby-OOo script).


Language for OOo can be done on OOoBasic, C++ Python and many other bindings,
Novell is working on the C# binding and is going quite good.


-- Alexandro Colorado Co-Leader of OpenOffice.org Spanish http://es.openoffice.org/


--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]



Reply via email to