Summary of NWI -- the page

[Matthew Woehlke]

Maciej Pilichowski wrote:
> On Tuesday 07 July 2009 22:20:05 Matthew Woehlke wrote:
>>> I disagree. Application launch costs, and user should not control
>>> all the time if this app quits, or not.
>> Um... but the point is, closing the window does *not* close the app
>> in these cases. (Well maybe if mail editor is separate app, but I
>> think not; 
> 
> Mail editor can be launched as standalone app, so I see one window and 
> I expect it will stay after closing document.

To be clear, if it is launched stand-alone, it /should/ stay after 
close-document. Only if it is launched as "satellite" of kmail would 
close-document close the window.

Personally I think it is a little weird for composer to be a separate 
app :-). Most e-mail programs (M$OE, Evolution, TB), the mail editor is 
part of the mail manager.

>> And if it is 
>> expensive to relaunch such satellite window, IMO app is doing
>> something wrong.
> 
> It depends, it could be part of the workflow, but external app after 
> all (like Kate as an editor).
> 
> But again -- we should end up with consistent UI, if user has to think 
> what will happen -- "is this part of the app or not" -- this would be 
> wrong.

Sigh. I don't know. I guess Diego's notions are starting to rub off.

Maybe we should just say 'close document can never close a window'. But 
then it must also be allowed to not exist (e.g. kopete windows).

I guess it /does/ work better for an interface designed from scratch. 
Unfortunately I expect there to be retraining issues...

>>> It should stay put until I am finished. And I am finished when I
>>> close the app, not the doc.
>> I am certainly finished chatting with someone without closing
>> kopete!
> 
> ? If you are finished, why do you not close the kopete?

Um. If I close kopete I am offline. And I have to restart it to get 
online again.

Kopete chat windows are one of those fun class of windows that start 
with "an open document" and cannot be empty or change to a different 
"document". (In this case, "document" is "chat session with a particular 
user".)

Do I recall right you have never used kopete? (Any IM client? How about 
konversation?)

>>> -- I launched you, because I have to write 5 emails. So stay put
>>> and don't go anywhere.
>> Hmm... is the problem that you need a "send and start writing new"
>> button, or that composer takes too long to re-launch from "write
>> new" button in kmail? If it was near-instant to launch, would you
>> still have a problem with close-document closing composer (but only
>> if launched from e.g. kmail and not launched stand-alone)?
> 
> Yes. Because I prefer if computer system is shaped like real-life. And 
> I get typewriter (well, not anymore) and I fill several pages. I 
> don't hide&get typewriter with each page.

I could make a counter-argument, though :-). KMail is like a desk, and 
messages are like sheets of paper you write mail on. When you are done 
writing, you put the paper in an envelope. The paper is now gone, you 
have to get a new piece of paper to write another letter.

(Note though I'm not talking about composer stand-alone. Only used with 
KMail.)

-- 
Matthew
Please do not quote my e-mail address unobfuscated in message bodies.
-- 
  ,= ,-_-. =.    Freedom to Use
((_/)o o(\_))  Freedom to Examine
  `-'(. .)`-'  Freedom to Share
      \_/     Freedom to Improve