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

List:       kde-usability
Subject:    Re: Delete, move and merge kedit, kate and kwrite
From:       "Manuel Amador (Rudd-O)" <amadorm () usm ! edu ! ec>
Date:       2003-04-05 22:53:50
[Download RAW message or body]

>
>
>"In general KDE consists only of SDI apps so Close is going to close the
>current window (or windows alike widge like tabs) while Quit quits the
>application as a whole"
>
This reflects the truth, but why should the user be aware of the fact 
that, behind the scenes, there's a single application juggling with 
several documents?  To fully take advantage of a spatial SDI interface,  
there should not be a Quit option at all.  It's not like users regularly 
close 27 windows of the same application, and it permeates 
implementation details to the user.

>close does not close a window, it closes a document.
>quit doesn't not kill the process (or all the windows), it closes a window.
>
>once everyone is on the same page regarding how Close/Quit actually works then 
>i'm personally more than excited to engage in both discussion and work on the 
>matter.
>
Can't "Quit" go?  Close is very clear -> it closes the current Window, 
whatever that implies (closing the file, closing the system monitor, 
closing whatever).  Quit is redundant, and Quit is confusing: on first 
sight, how is the user going to know that Quit closes all documents of a 
certain type (say, text)?  Quit's behavior isn't evident from the word.  
Besides, in English, quit can mean "give up".

_______________________________________________
kde-usability mailing list
kde-usability@mail.kde.org
http://mail.kde.org/mailman/listinfo/kde-usability
[prev in list] [next in list] [prev in thread] [next in thread]