Path: utzoo!attcan!utgpu!jarvis.csri.toronto.edu!cs.utexas.edu!usc!apple!sun-barr!lll-winken!gauss.llnl.gov!casey
From: casey@gauss.llnl.gov (Casey Leedom)
Newsgroups: comp.windows.x
Subject: Wherefore art thou UWM?
Message-ID: <40169@lll-winken.LLNL.GOV>
Date: 1 Dec 89 21:50:59 GMT
Sender: usenet@lll-winken.LLNL.GOV
Reply-To: casey@gauss.llnl.gov (Casey Leedom)
Organization: Lawrence Livermore National Laboratory
Lines: 21


  Two questions.  First the simple one:

    1.	Why doesn't "freeze" affect window instantiations in UWM.
	(I know which section of code is responsible.  I'm interested
	in why the authors of UWM decided not to have "freeze" only
	affect moves and resizes.)  I ask this because my GraphOn OptiMax
	200 X11 terminal doesn't cope well with UWM's assumption of
	infinite bandwidth between UWM and the display.

    2.	I'd ``fix'' this and submit a patch to MIT, but it seems to me
	that I saw a note going by from one of the MIT folk that said
	that UWM was going to be deprecated in R4.  Is R4 going to come
	with any window managers except those in the contrib area?  (I.e.
	are there going to be any in the core?)  And, what does this bode
	for UWM's future?  It's still the only window manager I've tried
	that I can stand.  (I've tried awm and twm.  They just get in my
	way.  (And no, my default shell isn't /bin/sh ... :-)) I have yet
	to try gwm, mwm, etc.)

Casey