Le 06/01/11 10:59, Carlo Strata a écrit :
What are we waiting for??????
For the NeoOffice project leaders to show an interest in collaborating ?
I haven't yet seen anything on the lists from any of the Neo devs, in
particular Patrick Luby. Perhaps he is just keeping himself to himself,
after all that is his free choice to do so if he so wishes.
Another point to mention is that NeoOffice makes very heavy use of the
Java framework on the Mac. Given the current "legal fog" surrounding the
use of "official" Java versions by Oracle (you might like to check out
why the Apache project has officially resigned from the Java cooperation
council), the LibreOffice devs are currently looking at minimising java
code intrusion into the current LibO code base going forward, something
that the NeoOffice project might not look on too favourably if it has
become the cornerstone of their OS integration on the Mac. The LibO Base
module is a prime candidate for change, as are some of the filter
implementations (FlatXML most notably).
At least one dev is working on de-java-ising XML filter functionality.
At least another is looking at trying to get SQLite to work better with
LibO, which if it works, may or may not become the replacement for
HSQLdb. At least the option will be there to try a different
embedded/embeddable database (if it works).
Unsubscribe instructions: E-mail to firstname.lastname@example.org
*** All posts to this list are publicly archived for eternity ***
Impressum (Legal Info)
: 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