On Tue, 2010-11-02 at 15:32 -0500, T. J. Brumfield wrote:
Can we get a list of all the components that require Java that would need to
be reimplemented?
To start a list we could add:
+ XSL transformations (an easy hack to replace by libxsl)
+ Base HSQLDB backend
+ Base report builder (using Pentaho IIRC)
+ Impress HTML export wizards
+ Possibly other wizards in Writer and Impress
+ Misc UNO extensions
With a list it would be easier to determine if it is feasible to replace
those components.
Removing Java completely is a No-go for me as this would prevent
developers to write extensions and automation in Java. There are
currently no other quick and simple way to extend OOo / LO for people
who don't really care about the internals. Removing all Java
dependencies from LO (and then removing the Java UNO bridge) would mean
that we will exclude:
* Java extensions developers & users
* Java external apps using LO
The JVM isn't started unless some Java code needs to be run... I would
go for removing as much as possible (mostly the XSLT and Base things)
but keep it around for the UNO bridge: this would help us gain on
performance.
--
Cédric Bosdonnat
LibreOffice hacker
http://documentfoundation.org
OOo Eclipse Integration developer
http://cedric.bosdonnat.free.fr
--
Unsubscribe instructions: Email to discuss+help@documentfoundation.org
Posting guidelines: http://netmeister.org/news/learn2quote.html
Archive: http://www.documentfoundation.org/lists/discuss/
*** All posts to this list are publicly archived ***
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.