Hi *, Replaying in general to the thread, that is based mainly on bug 121577.
The discussion about incompatibility, centered on this bug, is meaningless: bug https://issues.apache.org/ooo/show_bug.cgi?id=121582 is the real code-incompatible change, every extension developer will have to check the code and adapt it to API changes introduced by this task. It would be interesting to hear arguments against implementing the changes needed to perform the task for bug 121582. On Thu, Jan 17, 2013 at 12:24:15PM +0100, Bernard Marcelly wrote: > Of course an extension packager can be modified to the new addon syntax. > The problem is not here, it is that all existing extensions will not > work as designed unless they are each modified. Well, this is the concept of a mayor version change. Note that the mayor version change was not decided for these API/extension related changes; on the contrary, the mayor version change is a chance to perform API clean-up task that may imply incompatible API changes. Bug 121582 is one of these tasks, there are several other tasks for cleaning-up the API but human resources to perform them are small. > And modified extensions will not be compatible with previous versions > or with LibreOffice. Being compatible with LO is not OpenOffice's concern; in fact, they've introduced new API since early versions[1]; so the fact that extension can be installed on both programs is just a question of luck. [1] An example: http://api.libreoffice.org/docs/common/ref/com/sun/star/table/BorderLine2.html Regards -- Ariel Constenla-Haile La Plata, Argentina
pgpdfgIcPDtUv.pgp
Description: PGP signature
