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

List:       kde-look
Subject:    Re: quit/close was: User Interface Standards
From:       John Summerfield <summer () OS2 ! ami ! com ! au>
Date:       1999-09-16 0:27:48
[Download RAW message or body]

> zander@microweb.nl wrote:
> > 
> > My argument was that close should always be in place.
> > 
> > And on open: this would open a new window if the window contains a non-empt
> y
> > document.
> Would be a solution, BUT (BIG BUT ;-): kedit, kwrite, kword, mswindows,
> ... don't open a new window after pressing 'Open', if the window
> contains allready a document. They ask like "Do you want to save the
> document before opening?". The same with New: no new window will
> opened...

and that is bad design. I often WANT to have two documents open; I would 
prefer to not have to start the application twice. I can have several 
documents open with Lotus WordPro, with WordPerfect, with gnome-edit, with 
epm (OS/2 programmer's editor), with lpex (another OS/2 programmers 
editor), with tedit (a character-mode OS/2 editor).


The notion that one should close one document in order to open another is 
really stupid.


> 
> We can't put something into the standards, which acts completely
> different to standard-applications allready used.
> 
> New, Open, Save, Save As, Print... is clear for everyone. Personally I
> think you don't need to 'Close' a document (=> blank window). But I
> added it to the site, because I heard KWord is able to have blank
> windows.
> 
> So my suggestion: leave away the Close if your application doesn't
> support having a blank window.
> 
> Question: should we drop the Close completely? [Dangerous question ;-)]

Don't be silly. How else does one close one document without ending the 
application?

> 

-- 
Cheers
John Summerfield
http://os2.ami.com.au/os2/ for OS/2 support.
Configuration, networking, combined IBM ftpsites index.

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