-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
Hi
Am 04.11.11 19:27, schrieb Davide Dozza:
There are some compatibility problems. With LibO 3.4.3 the
extension can be installed but neither the custom bar nor the
configuration item are displayed. Therefore it seems the extension
code doesn't start.
So this is the point where I want to moot someting like an
"API-Taskforce".
It should be possible from my point of view that some devs take the
responsibility to check new code to avoid api-breaks. And put to the
conscience of all devs that it should be a top priority to avoid
breaking the API-compatibility (no matter if they are made in OOO or LO).
If we loose the extension compatibility we will loose a lot of good
reasons for OOo/LO in many scenarios an also a lot of good devs
working on Extensions.
- --
Mit freundlichen Grüßen
Uwe Altmann
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.9 (Darwin)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/
iEYEARECAAYFAk60WyIACgkQOTVzivhNo0J4dwCg1xD2g5EUhjQZ5apyGWB5v+ZL
TnkAn23bup0aHiIWiS9yElEgrpXDTSYl
=7LRz
-----END PGP SIGNATURE-----
--
Unsubscribe instructions: E-mail to discuss+help@documentfoundation.org
Problems? http://www.libreoffice.org/get-help/mailing-lists/how-to-unsubscribe/
Posting guidelines + more: http://wiki.documentfoundation.org/Netiquette
List archive: http://listarchives.documentfoundation.org/www/discuss/
All messages sent to this list will be publicly archived and cannot be deleted
Context
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.