Path: utzoo!attcan!uunet!bloom-beacon!EXPO.LCS.MIT.EDU!rws
From: rws@EXPO.LCS.MIT.EDU (Bob Scheifler)
Newsgroups: comp.windows.x
Subject: Re: User-WM communication
Message-ID: <8909221221.AA22077@expire.lcs.mit.edu>
Date: 22 Sep 89 12:21:23 GMT
References: <8909220829.AA00900@korfu.udac.uu.se>
Sender: daemon@bloom-beacon.MIT.EDU
Organization: The Internet
Lines: 19


	<windows jumping through hoops>
	And later let the window manager read this and act accordingly. 
	Isn't there any (non-standard) way to do this? If not, why is this so?

I'm sure you could invent a non-standard way.  There are window managers
that will read some client-specific resources from (at least) the server's
resource database, you can examine particular vendor window managers to
get details.  I'm sure you could invent a resources property to be stuck
on a client window for a window manager to read.  I don't know off-hand if
any window managers currently do that kind of thing.

But, what you seem to be asking is, "how come there isn't a standard way that
I can type arbitrary non-standard information at the command line of an
arbitrary client, on an arbitrary operating system, and have it not affect the
client but get transferred to the window manager?".  Well, we don't force
standardization of command line syntax, and no one to my knowledge ever
suggested (during the public review of the ICCCM) that this kind of transfer
mechanism was important or should be standardized.