https://bugs.documentfoundation.org/show_bug.cgi?id=127469
--- Comment #7 from Ulrich Windl <Ulrich.Windl@rz.uni-regensburg.de> ---
(In reply to Heiko Tietze from comment #6)
(...) My POV is that very seldom needed functions clutter the UI and
impacts usability (more things to learn, to maintain, to translate...).
If memory serves me right it was in LO 4 when the dialogs became "big and
almost empty", making me wonder why to waste so much screen space (in the
meantime they were re-filled a bit). So my point of view is that an UI done
properly can handle more feature than an UI done poorly without overloading the
user.
UI design is very much a matter of taste, but I noticed that some (personal
opinion follows) important features were dropped, some less needed (Avoiding
"useless") features were added, and some really bad "design solutions" were
kept (like the only palette available in Tools->Options: Well hidden and the
least important palette IMHO).
So leaving all taste aside: I still think importing and exporting palette files
in some well-documented formats is a useful thing to have. The "average day
user" probably never defined a new color or changed on in a palette, so that
user probably wouldn't ever see the "complicated UI" you are afraid of.
--
You are receiving this mail because:
You are on the CC list for the bug.
Context
- [Libreoffice-ux-advise] [Bug 127469] Allow import of color palettes in some "popular" formats · bugzilla-daemon
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.