Pedro wrote > The fact that the VBA is for Windows (and Mac?) is not related to locking > people in. VBA is a scripting language shared by all MSO programs to allow > automation.
I disagree. As my response upthread indicates, a macro language is designed to allow access to an API i.e., an implementation-specific method of manipulation that has nothing to do with interoperability, portability, or file format specifications. Pedro wrote > I think you are being an Open Source fundamentalist. Creating and using > macros doesn't drag you to the dark side of the force... No. But as Michael Meeks indicated (also linked upthread) it does make interoperability, portability, and transitioning from one product to another /significantly/ more difficult. Best wishes, Owen. -- View this message in context: http://nabble.documentfoundation.org/status-of-macro-in-ODF-interoperability-tp4116471p4116757.html Sent from the Users mailing list archive at Nabble.com. -- To unsubscribe e-mail to: [email protected] Problems? http://www.libreoffice.org/get-help/mailing-lists/how-to-unsubscribe/ Posting guidelines + more: http://wiki.documentfoundation.org/Netiquette List archive: http://listarchives.libreoffice.org/global/users/ All messages sent to this list will be publicly archived and cannot be deleted
