M. Fioretti wrote: > On Wed, Jun 08, 2005 13:54:43 PM -0400, Daniel Carrera > ([EMAIL PROTECTED]) wrote: > >> Top posting. >> >> I think that adding Javascript-like functionality would be a worthy >> goal. In fact... we should Javascript itself the first macro language >> and make it do everything Javascript currently does on web pages. > [...] > >> In any event, back to your note. Having Javascript work with OD files >> would be the way to go if OD were to work with the web of the future. >> > > Me, I've nothing serious against JavaScript, except, maybe, the fact > that if one goes Python, Perl or similar, he may reuse some of that > knowledge in other areas of computing.
Please let me repeat that the runtime language should be irrelevant, binding your application to a particular scripting language is dumb and not future-proof. The concept of language bindings as offered by UNO, COM or .NET is very powerful and allows to switch to other languages in the future. Of course for a standard you must select a mandatory language that everybody needs to support but which language this might be is completely irrelevant in the beginning. The language binding concept allows you to add further mandatory languages later on if it seems to be appropriate. It's the API that counts and that must be standardized. If this is done, you can think about the preferred language and of course you should choose one that is standardized by itself (that saves time ;-)). JavaScript would be a good choice because an ECMA Standard exists. Basic obviously would be a bad choice, I don't know if Python can be seen as standardized. 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]
