Date: prev next · Thread: first prev next last
2013 Archives by date, by thread · List index

On Mon, Mar 4, 2013 at 1:46 AM, Fernand Vanrie <> wrote:
On 4/03/2013 8:27, M. Fioretti wrote:

On Mon, Mar 04, 2013 08:16:25 AM +0100, Fernand Vanrie wrote:

99% percent , changes comes and will come from incompatiliteis in de API.
for now this is OK, small changes from version to version, but
nothing who not can been repaired or handled with the code( basic)

I knew that. The sense of my question is, is there is a list of things
to avoid beforehand, rather than wait that they break and fix the

thats more a question for the developers list .  and fore the aOO counterpart


The reason why nobody responded is no one knows, and it will generally
get worse over time as the codebases diverge. It is sort of like the
Java: "write once, test everywhere" situation.

One of the unintended consequences of the fork is the various ways it
makes things more difficult for third-parties. Users will generally
pick one product, but extension developers have a more complicated set
of choices because they may want to support multiple brands. Here is
an article I recently wrote about the power of brands that may be

The good news is that in the free software world, code flows with less
friction. Any typical (non-enterprise) who really wants an extension
will likely be able to install a specific version of the product if it
is required. It is just a download.

Good luck!



Unsubscribe instructions: E-mail to
Posting guidelines + more:
List archive:
All messages sent to this list will be publicly archived and cannot be deleted


Privacy Policy | Impressum (Legal Info) | Copyright information: Unless otherwise specified, all text and images on this website are licensed under the Creative Commons Attribution-Share Alike 3.0 License. This does not include the source code of LibreOffice, which is licensed under the Mozilla Public License (MPLv2). "LibreOffice" and "The Document Foundation" are registered trademarks of their corresponding registered owners or are in actual use as trademarks in one or more countries. Their respective logos and icons are also subject to international copyright laws. Use thereof is explained in our trademark policy.