Date: prev next · Thread: first prev next last
2010 Archives by date, by thread · List index


On 10/12/10 21:18, Friedrich Strohmaier wrote:
All I am going to add is: "which user prefers single-clicks for some
status bar items and double-clicks on others, while some are not
clickable at all?".
One who has been told / has learned to do so and doesn't bother on any
theory of userfriendly UI :o))..

"Which user wants to launch dialogs when clicking
on apparently empty areas in the statusbar?"
see above..

and finally "which user wants 2 separators between icon areas that are
really empty?"
One who has learned to (double-)click the fourth area will be confused
what to do now.

"which user wants exclamation marks for default situations rather than
suitably subtle icons that show modified doc status?" :-)
Again: see above. ("You told me to click the exclamation mark - where
should I click now?").

Unfortunately, this then plays havoc with the next bunch of users - who
have at least partially learnt how to use the interface. One thing the
normal user (one step above the "blindly follow the cheat sheet" monkey)
values, is a *consistent* interface.

And I know there's no such thing as "intuitive", but I still compare
Word and WordPerfect ... I moved to WordPerfect from my previous word
processors from choice, I didn't have to learn WordPerfect, it was just
"obvious". I *still* (despite using it for many years) don't know how to
use Word properly.

Cheers,
Wol

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.