Daniel Carrera wrote:

> Marco Fioretti wrote:
> 
> >    [snip: OpenDocument and freedom] This loses
> >    a *lot* of relevance if there is no defined path to standardize
> >    macros and spreadsheet formulas, and the will to follow 
> it.
> 
> Well, there is a defined path for spreadsheet formulas. As for 
> macros,
> the issue is more tricky because a macro is a program that tells 
> the application to do something.

Well, not exactly, if I have understood it correctly.
A macro is a small program written in some _language_. It is NOT
the code _and_ its interpreter. The latter, yes, is definitely not
portable. This is what I'm thinking about:

1) Python interface for opendocument, ie set of function definitions
   that read/write odt files and their elements

2) different *implementations* of those functions for KOffice, OO.o,
   anything else. Just like there is *one* Python language, but
   different binary interpreters for it on Linux, Windows etc...

3) Then, you and I write a macro in "Python calling the library
   defined in 1) above" on whatever platform and once...

4) that Python _code_ is zipped with everything else in the .odt
   file, just like StarBasic code in .sxw files today...

5) we can then send the .odt file to anybody with:
    any .odt program (OO.o, KOffice...) + Python + his own
    specific implementation of 1) above...

6) and he will be able to run the macro, happily ignoring with
   which combination of .odt-program and operating system it was 
   created.

I have written Python above because it is already useable *today*,
or so I understand, both in OO.o *and* KOffice, or in any case much
more common in computing than StarBasic, so I'm seriously starting
to think that it is a much better choice to solve this problem.

Any feedback on the flow above, from suggestions on how to implement
it to (polite, please! ) strong criticism is welcome.

Before I forget: if this does make sense, why not add it to the
list of "google summer of code" OO.o projects? Just in case
somebody felt like doing it?

Ciao,
Marco




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

Reply via email to