Mathias Bauer <[EMAIL PROTECTED]> writes: > What I especially wouldn't like is the following situation: I have > written an extension that runs fine in, say, OOo 2.x. I also didn't use > any types that have been changed incompatibly in OOo3.0 but as this > release is announced to be API-incompatible my extension is not usable > reliably. How can we avoid that? How can an extension find out whether > it is still compatible to the current OOo version? > Hi Mathias,
there's a relatively recent thread about this topic in [EMAIL PROTECTED] > I hate how it is done in TBird and FFox where extensions are disabled > just because the version number changed but still run fine after some > manual fiddling in the version information of the extension (something > end users shouldn't need to do). > But that's the only safe way to do this, for them. BTW, telling from past experience here: even if API stays compatible syntactically, there's absolutely no guarantee that the semantics haven't changed, and the extensions stops working anyway. I don't see much value in this UNO API compatibility discussion, unless we deal with this end-to-end. An acceptable level of future-proofness can IMO only be achieved by either QAing against all extensions (and disabling what hasn't - that's the Mozilla approach), or running extensions in a sandbox (out-of-process might be good enough here). Cheers, -- Thorsten --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
