Hi Cedric, *
On Wed, Nov 3, 2010 at 12:14 AM, Cedric Bosdonnat
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
To start a list we could add:
+ Base HSQLDB backend
That would mean: ship a different database with by default, but you
would still need that backend otherwise you'd introduce a major
incompatibility with previous versions.
That list is missing
+ (free) search in Help (uses lucene)
And I fully agree - just dropping java just for the sake of it is a
very, very bad idea.
The JVM isn't started unless some Java code needs to be run...
Exactly (and that reminds me of a annoyance in OOo builds, that if you
don't have a JRE configured, but access features that would require
java, you don't only get one dialog stating you need java for that
functionality, but it can cause tens of those (e.g. with macro-related
go for removing as much as possible (mostly the XSLT and Base things)
I don't really see a chance for base unless you want to duplicate base.
But honestly: Nowadays java isn't that ressource-hog it once was, it
loads much faster (and of course once it is loaded you don't really
notice a difference).
(Yes, I personally do like java, and I'd not create a code-heavy
extension in any other language without a good reason)
Unsubscribe instructions: Email to email@example.com
Posting guidelines: http://netmeister.org/news/learn2quote.html
*** All posts to this list are publicly archived ***
- Re: [tdf-discuss] Java dependency (continued)
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