Ian wrote:

> At the risk of getting flamed I think that Marco has a good idea, I
> would like to bounce some ideas about how it could be implemented.

Oh, until now I don't see that anybody denied that. It just seems that
Marco doesn't know how things work and why it is so complicated to
implement this idea.

There is nothing bad with it, finally Marco isn't a developer, but I
think we should try to understand what we are talking about.

For me it is necessary that any possible "standard" for macros is
language agnostic so that it gives you the choice of the macro language.
Of course the possibles languages should already follow accepted
standards also or need an also standardized runtime. The main
standardization work needs to be done on the API.

> I can see two, not mutually exclusive, possibilities:
> 
> 1. With XML forms and probably JavaScript (as I think this is currently
> the recognised standard for the web, although I too would prefer Python)
> it should be possible to implement Marco's interactive learning
> scenario.

Yes and no. It depends on the desired function set.

> After more discussion if this, or some other idea is seen as workable,
> then suggest an update to the open document standard.

No, IMHO this goes beyond the OpenDocument standard. I also like the
idea of standardizing a basic set of functions for scripting, but that
should be done in another process, not in the OASIS Open Document TC.

Adhering to standards always is a voluntary decision. If developers
stick to the Open Document standard they do it because they think
standardization is a good thing. So I assume their willingness to
support a possible scripting standard is not influenced by the fact
wether this standard is part of Open Document or another standard solely
for document scripting.

Best regards,
Mathias

-- 
Mathias Bauer - OpenOffice.org Application Framework Project Lead
Please reply to the list only, [EMAIL PROTECTED] is a spam sink.


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

Reply via email to