M. Fioretti wrote:
"Add-ons created today will still run with future versions of OO.o because the API is under complete control and kept compatible"
"Complete control" sounds really bad. OOo has just as much control over it's APIs as Mozilla does over Moz APIs etc. OOo just makes an effort to keep them constant.
because this is what was explained to me when I asked. The comment instead suggests this is not true, when recommending "extentions have to be coded such that they work in future releases".
Most things you find in OOoMacros are not add-ons. In fact, I don't think I've seen a single one. They are always OOo files with macros in them. Some of them include self-made installers to copy the macro and make it available OOo-wide. But that doesn't make it an OOo package, and you can't blame OOo packages if a self-made installer breaks. Though, if it broke because OOo changed it's API, that's different.
Cheers, Daniel. --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
