Path: utzoo!attcan!utgpu!jarvis.csri.toronto.edu!mailrus!wuarchive!cs.utexas.edu!uunet!ncrlnk!wright!odin!adatta
From: adatta@odin.wright.edu (Amitava Datta)
Newsgroups: comp.windows.x
Subject: Re: Window Managers and Client Menus
Message-ID: <681@thor.wright.EDU>
Date: 26 Sep 89 21:36:18 GMT
References: <663@thor.wright.EDU> <654@thor.wright.EDU> <1839@bacchus.dec.com> <3198@arisia.Xerox.COM>
Sender: news@wright.EDU
Lines: 20

In article <3198@arisia.Xerox.COM>, janssen@holmes (Bill Janssen) writes:
> In article <671@thor.wright.EDU>, adatta@odin (Amitava Datta) writes:
> >... At least we will have a uniform interface to all menu. 
> 
> Well, not really.  Only to those clients that use *your* menu package,
> which is built into a window manager.  Clients that use the Motif or
> Open Look packages will present their menus themselves, and will 
> look different from your menus.  You really can't win.
> 

X WMs try to stick to the ICCCM specification. What I am hoping to get
out of this discussion in comp.windows.x is a good reason why the
Client Menu Handling shouldn't be part of the ICCCM spec. for X WMs.
If it is made part of the standard interface then all clients can be
"encouraged" to use this so that the user (the guys that we write
programs for) will enjoy the "uniform interface to all menus"; just
the way we encourage clients not to use the `override_redirect'
attribute. 

Amitava Datta (adatta@cs.wright.edu)