Actually, if we do adapt and name our theme, our goal, like any other
product in our "arsenal of products" would be to use it to our marketing
advantage. We could easily market it as a theme optimized for screenshots
and people would gladly download our "LibreOffice Theme" for this reason and
not necessarily for LibreOffice reasons.
Clearly, maintaining an own theme is a lot of work. For instance, I
don't know if Clearlooks has already been ported to Gnome 3.
Another thing to note is that
a) Mac theming is not customisable at all today and
b) Windows theming is far less flexible than in the 2000 era (well,
the legacy theming engine from Windows 2000 and earlier is still
present, but it simply doesn't look temporary any more). It also isn't
easy to install a third-party modern theme engine like Clearlooks in
XP or later, additionally the free ones I've seen were all not very
high-quality ones (I think they also have to be signed in Vista and 7,
but I'm not sure). In Vista's and 7's Aero mode one can only choose a
hue for the window frame.
c) Gnome 3 theming is currently also not customisable via GUI, even
though it has a very flexible CSS theming engine now.
So that leaves KDE fully configurable but this is probably the least
used among the platforms.
A practical solution would be to offer a download package for Gnome
and KDE (where all that should be changed should be the colors of a
standard theme like Clearlooks, plus maybe a .fonts.conf to configure
font display), and giving Windows Vista/7 users hints as to how to
change the window frame hue in their system.
If we are going to be serious about quality document production, website,
etc. then we should maybe consider adding the care of the LibreOffice theme
to the list of responsibility of the dev team. I imagine that we could also
enlist the help of the website team experts in this domain. It could be a
shared responsibility and it doesn't necessarily mean that it is "someone's"
responsibility but more of a responsibility of the dev/website or dev team
for whoever would like to take it up.
Here's an idea of mine: a public screenshot machine where after a
login people can easily make screenshots within their browser windows.
However, it would be difficult to make screenshots that require
devices or OSs not installed on the machine. Additionally you'd need
to make sure that people can upload example files etc. before they
start the session and can download their screenshots afterwards.
(Please note, I am just throwing this out here and have no idea how
hard this would be to implement!).
There were also some questions about FreeSans being opensource, yes,
it is. It can be downloaded from here:
http://savannah.gnu.org/projects/freefont/ . It should share most of
its metrics with Arial/Liberation Sans, aside from its line-height
being much higher—I suppose that's because of the comprehensive
language support. But if you've already decided, stick with
Unsubscribe instructions: E-mail to firstname.lastname@example.org
Posting guidelines + more: http://wiki.documentfoundation.org/Netiquette
List archive: http://listarchives.libreoffice.org/global/design/
All messages sent to this list will be publicly archived and cannot be deleted
Re: [libreoffice-design] [VI] Consistent theme for screenshots · Jean Hollis Weber
[libreoffice-design] Re: [VI] Consistent theme for screenshots · eskroni
[libreoffice-design] Add new modules: SCAN SUITE "a la" nuance paperport" / accounting, and e-billing · Miguel Mayol Tur
[libreoffice-design] Re: [VI] Consistent theme for screenshots · Marc Paré
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