Hi, :-)
It's been an interesting thread. I read Mirek's blog posts:
http://clickortap.wordpress.com/2010/10/14/citrus-ui/
http://clickortap.wordpress.com/2010/10/15/the-citrus-menu/
I also read the Rennaissance FAQ:
http://wiki.services.openoffice.org/wiki/Renaissance/FAQ#Official_Statements
Different users and devices call for different configurations, but
IMHO full-blooded themeability would provide most of the answers.
A lot of stuff is already configurable via Tools/Options or the GUI.
Gnome gives a lot of control, for instance.
However, I'd love to see that taken further in a full-blooded
themes/skins system. Given the variety of devices that run a Linux- or
Windows-based OS (and the variety of form factors), choice and
flexibility are important. But, since LibO is a multi-platform suite,
the right solution is delicate to achieve.
Marik, IMHO your Citrus menu looks pretty good as one initial
approach. I guess I'd need to try it out to say more.
UI is an aspect of LibO that interests me a lot. I'd be pleased to
help out if you need stuff done on Gimp/Photoshop, or in some other
way. Feel free to contact me if you like.
David Nelson
--
E-mail to discuss+help@documentfoundation.org for instructions on how to unsubscribe
List archives are available at http://www.documentfoundation.org/lists/discuss/
All messages you send to this list will be publicly archived and cannot be deleted
Context
- Re: [tdf-discuss] UI proposal (continued)
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.