On Sun, 11 Dec 2011 15:39:08 +0100, Korrawit Pruegsanusak
<detective.conan.1412@gmail.com> wrote:
Hello all,
/me separate this into new thread. :)
On Sun, Dec 11, 2011 at 11:47, Korrawit Pruegsanusak
<detective.conan.1412@gmail.com> wrote:
So, do we really support classic and industrial themes? I've found
them listed
on ooo_custom_images [1], but I'm not sure if it's relevant.
[1] http://opengrok.libreoffice.org/xref/core/ooo_custom_images/
[cut]
additional infos about this on the bugtracker:
https://bugs.freedesktop.org/show_bug.cgi?id=38175
basically, the Classic theme was removed in LibO 3.4.0
but you can manually enable it again downloading a 3.4.x compliant
theme ( images_classic.zip ) from the issue tracker and copying it the
proper location:
\Bin\LibreOffice 3\Basis\share\config (in Windows, don't know if it's the
same in Linux and Mac)
this works in 3.4.x but doesn't work on 3.5 master
my guess is that in LibO 3.4.x the devs just removed physically the
images_classic.zip file but the software still has some code somewhere
pointing
towards that file.
indeed if you put a images_classic.zip file under 3.4.x you can enable the
classic theme.
however if you rename the images_classic.zip with something else (i.e.
images_dummy.zip) LibO 3.4.x fails to recognize that theme.
probably the code in 3.5.x has been cleaned and there's no place for the
classic theme yet, but just for the other themes (Tango, Galaxy etc. etc.)
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.