KMail key binding and the User Interface Guidelines

Frans Englich frans.englich at telia.com
Mon Feb 2 01:32:04 GMT 2004


On Monday 02 February 2004 01:31, Henrique Pinto wrote:
> Hi Robin!
>
> I'm forwarding your message to the kde-usability and kmail-devel
> mailinglists, where it is likely to get more attention.

I, who haven't taken part in the discussion, have no difficulties in finding 
the issue interesting ;-)

To widen our horizons; a similar issue was discussed during the string freeze 
- whether Kopete should use <ctrl+enter> or just <enter> to send messages.

The ctrl+enter camp argued that it was consistent with other kde apps, a 
logical behavior since it was a multi line edit and it was what the 
guidelines said(all arguments true). ctrl+enter was simply the Right Thing, 
by no doubts the most "beautiful" solution.
Those in the other camp argued that most other IMs used <enter>. Using 
ctrl+enter would confuse a lot of emigrating users, as a couple of KDE 
reviews had indicated. This arguments were also true.
Consistency intra KDE versus consistency with the "world" outside KDE - a 
though call.

There is one big problem when not following policies - it halts KDE 
development. Regardless of how small the change is it always means a long 
discussion. This process is not bearable and different "solutions" have 
emerged. For example, behavior/functionality issues are solved with the 
glamorous "make it configurable". So for the ego of KDE, ensuring development 
is efficient, policies are a Good Thing.
If we do not stick to policies it will mean, in the long run, inconsistency 
intra KDE, and that is perhaps more worse than inconsistency with "outside" 
apps. On the other hand, then there will always be cases where shortcuts will 
be plain wrong. 
If we decide to stick to the guidelines we must /really/ stick to the 
guidelines and the cases where we should not stick to it, are very very very 
rare, and are just as stunning, "forbidden", and just absolutely right as 
when the Pinguin King ripped out the memory system in 2.4, to use a metaphor.

Sticking to the guidelines are the far easiest way to go, and protects us from 
"run a way" hackers.. The result when only looking at KDE is very nice, but 
with a touch of "screw everyone else". In either case, it's about compromise.


			Frans

___________________________________________________
This message is from the kde mailing list.
Account management:  https://mail.kde.org/mailman/listinfo/kde.
Archives: http://lists.kde.org/.
More info: http://www.kde.org/faq.html.




More information about the kde mailing list