[prev in list] [next in list] [prev in thread] [next in thread] 

List:       kde-usability
Subject:    Re: Ctrl-Q vs. Ctrl-W vs. Alt-F4
From:       Markus <kamikazow () web ! de>
Date:       2009-01-11 19:15:39
Message-ID: 200901112015.39647.kamikazow () web ! de
[Download RAW message or body]

Am Sonntag 11 Januar 2009 18:32:17 schrieb Celeste Lyn Paul:

> > No. Function should be one meaning and not be over smart. If you want
> > to close the window, please press the appropriate key. I don't get it
> > why it is not possible to press ctrl+q (example).

Both 
http://wiki.openusability.org/guidelines/index.php/Appendices:Keyboard_Shortcuts
and http://techbase.kde.org/Projects/Usability/HIG/Keyboard_Shortcuts describe 
Ctrl-Q as "Quit the application", not "Close window".

Firefox and OpenOffice -- two hugely popular applications -- use Ctrl-Q to quit 
the entire application.
I don't understand why KDE can't follow their lead. Is this due the NIH 
syndrome? Shouldn't we also aim for consistency with non-KDE apps?


> I agree.. Ctrl+W should never close a window. This especially doesn't make
> sense when the user has the "hide tabbar when only one tab is open" option
> turned on.

I don't understand this, too.
Eli MacKenzie described Ctrl-W as close-the-current-view. Why is a tab a view, 
but not a window?

I'm really, really confused why it is expected that common users have to 
understand the technical difference between Dolphin windows being individual 
instances of the app, while Firefox windows are not and how making a tab "go 
away" with Ctrl-W is something different to making a window "go away".
Please enlighten me.
_______________________________________________
kde-usability mailing list
kde-usability@kde.org
https://mail.kde.org/mailman/listinfo/kde-usability
[prev in list] [next in list] [prev in thread] [next in thread]