Hi Bernhard, hi Paulo!
Just a few thoughts, although I really know that I didn't follow this
topic very closely :-\
Am Montag, den 18.04.2011, 20:21 +0200 schrieb Bernhard Dippold:
Hi Paulo, all,
...
Paulo José Amaro schrieb:
...
Shorting the discussion, we need higher versions to Tango and Galaxy
mimetype icons, right? Ok, I think I can help on it. I'll look in the
Bugzilla and see what I can to do.
This would be great! Oxygen is described as non-existent, so this would
be another task to work on.
I'm sorry to appear a bit disruptive, but I'm unsure how much benefit we
gain by adapting all the icons for all the themes. My very personal
opinion is to - at least at the moment - should provide something that
works good as a default (e.g. Tango on Linux, Galaxy on Windows, ??? on
Mac). Again, this shows that we really need some reasonable strategy how
we want to deal with the platforms. What do you think?
For example, there might be more serious problems with Tango icon
"placeholders" having an inaccurate metaphor for certain features. Or,
we might start to develop the visual design for LibreOffice 3.5 - with
motif and new graphic sizes and information dialogs. Or, we need some
new icons for the StartCenter - currently we still use the Oracle
branded ones (gray).
...
I'm not quite sure if we need to follow the color styles of the
different themes, because this would mean to reduce our consistency on
different platforms and with different themes. There is no common color
palette for Tango, Galaxy and Oxygen, so we don't have any chance to
comply with all of them, if we want to stay consistent.
As I said in another mail - do we want to align our branding with other
FLOSS related projects? For example, if it fits, we might align with
what the Gnome guys do ... and maybe we are able to save some effort
with regard to standard icons and stuff.
Just as an example, here is what the Gnome guys did ...
http://jimmac.musichall.cz/log/?p=1145
Please consider this as an idea that might be valuable in the long-run
if we address larger topics ... at the moment, we should still work on
fixing what we have.
A question not very related to, anyway (sorry if it was already replied):
Why can't we use SVG files to icons, otherwise bitmap converted ones? I know
Ubuntu support SVG icons and they don't lost quality on resizing. Would it
because other operational systems?
We can, but we can't use them inside LibreOffice.
At least this is what I read from the Google Summer of Code proposal here:
http://wiki.documentfoundation.org/Development/Gsoc/Ideas#Use_svg_for_LibreOffice_icons
Another point I mentioned already in the bug report: I don't know an
easy way to extract single SVG files for each icon from the central
document. I don't want to copy and paste them manually every time when
they have been updated...
Same for me ... but we just want to change the colors, this should be
easily doable via a script that searches&replaces within the SVG file.
Mmh, this mail raises more new questions than it might help to answer
the old ones ... sorry.
Cheers,
Christoph
--
Unsubscribe instructions: E-mail to design+help@libreoffice.org
Posting guidelines + more: http://wiki.documentfoundation.org/Netiquette
List archive: http://listarchives.libreoffice.org/www/design/
All messages sent to this list will be publicly archived and cannot be deleted
Context
Re: [libreoffice-design] LibreOffice Icons · Tobias Bernard
Re: [libreoffice-design] LibreOffice Icons · Christoph Noack
Re: [libreoffice-design] LibreOffice Icons · Paulo José
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.