Path: utzoo!utgpu!jarvis.csri.toronto.edu!mailrus!ames!pasteur!ucbvax!tut.cis.ohio-state.edu!cs.utexas.edu!uunet!ncrlnk!ncr-sd!hp-sdd!hplabs!hp-pcd!hpcvlx!ben From: ben@hpcvlx.HP.COM (Benjamin Ellsworth) Newsgroups: comp.windows.x Subject: Re: X Toolkit XtCWQueryOnly and ICCCM window managers Message-ID: <100920071@hpcvlx.HP.COM> Date: 25 Apr 89 21:45:18 GMT References: <733@harrier.ukc.ac.uk> Organization: Hewlett-Packard Co., Corvallis, OR, USA Lines: 35 > The real problem is that the toolkit doesn't seem to make Shell > widgets special enough. Unlike other widgets, they are subject to > arbitrary size change at any time through an agency that will not > brook questions or disagreement. Hmmmm??? All widgets must provide a "resize" procedure which must be able to handle an arbitrary size change without *any* questions or disagreement. The acutal "agency" may be somewhat different, but the requirement is identical. > ... A client should work correctly with any top-level window > geometry. ... I think that you have missed the point. The desire is not for client control of geometry. The desire is for the client to be able to initiate and negotiate a change in geometry (much like a widget can request and negotiate with it's parent). Why shouldn't a client be able to negotiate a geometry with the window manager? In fact, a possible model would be to consider the window manager to be the "parent widget" of all the clients on the screen. Geometry management (in terms of protocol) between clients is then identical to geometry management within clients. > David. ----------------------------------------------------------------------- Benjamin Ellsworth | ben@cv.hp.com | INTERNET Hewlett-Packard Company | {backbone}!hplabs!hp-pcd!ben | UUCP 1000 N.E. Circle | (USA) (503) 750-4980 | FAX Corvallis, OR 97330 | (USA) (503) 757-2000 | VOICE ----------------------------------------------------------------------- All relevant disclaimers apply. -----------------------------------------------------------------------