Path: utzoo!attcan!uunet!bloom-beacon!BRILLIG.UMD.EDU!don
From: don@BRILLIG.UMD.EDU (Don Hopkins)
Newsgroups: comp.windows.x
Subject: Window Managers and Client Menus
Message-ID: <8909230138.AA13090@brillig.umd.edu>
Date: 23 Sep 89 01:38:06 GMT
References: <291@auto-trol.UUCP>
Sender: daemon@bloom-beacon.MIT.EDU
Organization: The Internet
Lines: 28


   Date: 21 Sep 89 22:30:38 GMT
   From: usc!cs.utexas.edu!ico!auto-trol!marbru@bloom-beacon.mit.edu  (Martin Brunecky)

   In article <653@thor.wright.EDU> adatta@odin.wright.edu (Amitava Datta) writes:
   >If you are building an X client and don't quite like the Xt support
   >for creating popup menus you may want to consider the following:
   >
   >  Why not have the X window manager display and manage menus for clients?
   >  (Of course, the window manager would need to inform the X client when
   >  a menu item gets selected)

   I vote NO !
   Pretty soon, somebody else would like the Window Manager to do this,
   taht and even more. After a little while we'll have Window Managers
   that do everything in the world, but nothing RIGHT.

Oh, come on, that's what extension languages are for! Emacs does
everything in the world, but there sure are a lot of people who would
flame you to a cinder if you said "Emacs does nothing right!" (But
let's not go into that subject on /this/ news group.)

Anyway, there's no reason the window manager and the menu/toolkit
manager have to be the same program.  There's also no reason they
couldn't all run in the address space of the window server (i.e.
X11/NeWS).  A good solution should support both possibilities.

	-Don