jonathon schrieb: > What I was thinking of was a save function/option that > created some_document_name.odf and > some_document_name.macros. some_document_name.macro > contains only the macros that are used with the document. > > I'm thinking of Joe Sixpack here, who doesn't know what an > IDE is, much less how to use it.
Possibly we are talking at cross-purposes. If was talking about the people who created the macros. They could use the "export" functionality of the IDE (that they had used to write the macros) to create an extension containing the macros instead of putting them into the templates or documents. If their admin installs the extension afterwards all users that are the audience for the documents and templates can use it without being bothered by a dialog asking them for permission. > Both of those macros ( OOoDic & OOoFont ) provide required > functionality for OOo. [FWIW, I wouldn't be surprised to see > OOo_Install_Grammar_Checking as well. This is a macro that > installs and configures Grammar Checkers.] > > The issue is whether such tools should be hard coded into > OOo, or soft-codes with macros. IMHO none of them. They should be deployed as extensions. And in this case it doesn't make a difference whether they have been written in Basic, Java, Python, JavaScript, BeanShell, C# or C++. >> The unbundling wouldn't cause a lot of coding in OOo. And why should it >> require changes in ODF? Macros are not part of ODF. > > Somewhere in the ODF specifications is a note on how to > handle macros. Unbundling macros from the document would > require the specifications to change to exclude the > possibility of macros being part of the document. We didn't need to exclude the possibility of macros just because OOo decided not to use them. Even if ODF mentions macros somewhere it neither specifies them nor makes them mandatory. OOo could specify that it never puts macros into documents nor executes any of them at any time. That would be enough. Again, I'm afraid this could make users angry. Ciao, Mathias -- Mathias Bauer (mba) - Project Lead OpenOffice.org Writer OpenOffice.org Engineering at Sun: http://blogs.sun.com/GullFOSS Please don't reply to "[EMAIL PROTECTED]". I use it for the OOo lists and only rarely read other mails sent to it. --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
