--- On Wed, 11/1/12, Onyeibo Oku<firstname.lastname@example.org> wrote:
From: Onyeibo Oku<email@example.com>
Subject: Re: [libreoffice-users] Re: re: So what's with LibO 3.5?
To: "Libre, Users"<firstname.lastname@example.org>
Date: Wednesday, 11 January, 2012, 18:06
3.5 is the way forward. I'm running it and I'm enjoying the experience :)
I just wish there's a better icon theme or is there a way to throw the UI open to system's icon
theme. I use faenza on GTK3 (fedora 16, Gnome3)?
Hmm, the call-out leaders for comments didn't get reviewed. Sometimes comments on a phrase overlap.
It should be better to use highlights rather than arrowheads for the 'comment' call-out(balloon). I
use this feature a lot :(
I'm happy to 'miss' the conspicuous margin borders ... Just neat.
Java 1.7 support? Thought the idea was to liberate LibreOffice of the Java dependency in order to
improve performance. Great, my custom-developed extension works as expected. I'm glad pyuno didn't
get broken. Next I'll be testing the speed of creating about 20sheets within a loop. 3.4 had speed
Until then ... Well done LibreOffice team!
from email@example.com :)
Date: Wed, 11 Jan 2012 06:00:32
Subject: [libreoffice-users] Re: re: So what's with LibO 3.5?
Gérard Fargeot wrote
The Release Notes page fails to mention that LO 3.5 now supports Java 7
(1.7). In fact if you have both Java 6 and 7 you can select which one to use
in Tools, Options, LibreOffice, Java
View this message in context:
Sent from the Users mailing list archive at Nabble.com.
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