Marco Fioretti wrote:
But this addon would not be embedded in an .odt paragraph (at
least, not in the current and near-future OOo releases).
Why not, if I may ask?
Uhhm... because no such functionality is implemented yet.
May I ask... is there a reason why a .odt file is needed but
an addon won't work for you? (provided that the add-on works
whenever OOo is installed).
Fair question, but you partly answered it yourself.
I did? wow! ;-)
OpenDocument is one thing, OO.o another. Who can assume that the
latter *will* be installed wherever the former is used? Especially
in 2/4 years, if OpenDocument is to become the truly universal
that we keep saying etc etc...
Ah.
I am not aware of Python macros being part of the OpenDocument spec.
Come to think of it, I don't know how OpenDocument deals with macros.
Back to my training class example: a portable macro embedded into
an .odt file is what you could use to distribute tutorials or any
other interactive educational material where there is scarce bandwidth
and/or PCs not powerful enough to run OO.o. Ditto for CDs attached
to magazines or books.
I very much doubt that this is possible. A macro always uses the OOo
API, and this API has no connection with OpenDocument.
Teacher writes on OO.o, students learn on KOffice. Or vice-versa.
That's why I said "embedded into the .odt file". Of course, if
(in the conditions above) there is any other solution which has
the same end result for the student/user is OK, but is there?
I don't think there is. But ask Gary, he's the OpenDocument guru.
Cheers,
Daniel.
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
