Path: utzoo!attcan!uunet!mcvax!guido
From: guido@cwi.nl (Guido van Rossum)
Newsgroups: comp.windows.x
Subject: Re: X Toolkit Question
Message-ID: <328@piring.cwi.nl>
Date: 19 May 88 14:20:19 GMT
References: <2479@mandrill.CWRU.Edu> <8805161424.AA16703@LYRE.MIT.EDU> <10039@agate.BERKELEY.EDU> <4992@eagle.ukc.ac.uk>
Reply-To: guido@cwi.nl (Guido van Rossum)
Organization: The Royal Society for Prevention of Cruelty to Amoebae
Lines: 22

In article <4992@eagle.ukc.ac.uk> rlh2@ukc.ac.uk (Richard Hesketh) writes:
>>How does a toolkit program iconify itself?
>
>static void
>closewin()
>[...]

OK, but I object to the name 'closewin'.  In my opinion, 'closing' a
window destroys it permanently; 'iconifying' a window leave an icon
around from which it can be restored exactly.  Supporting evidence: the
'close' buttons on xmh, for example.  Also, 'closing' is the
application's task, while 'iconifying' is mostly done by the window
manager (although there are certainly cases where applications want to
explicitly (de)iconify themselves under certain circumstances).

Mind you, I don't really mind how you call your functions, but I do
object to two different meanings assigned to the notion of closing a
window.  We need to set this straight.  What do *you* think?

--
Guido van Rossum, Centre for Mathematics and Computer Science (CWI), Amsterdam
guido@piring.cwi.nl or mcvax!piring!guido or guido%piring.cwi.nl@uunet.uu.net