Path: utzoo!censor!geac!jtsv16!uunet!cs.utexas.edu!tut.cis.ohio-state.edu!ucbvax!pasteur!dent.Berkeley.EDU!davidh
From: davidh@dent.Berkeley.EDU (David S. Harrison)
Newsgroups: comp.windows.x
Subject: Re: User-WM communication
Keywords: clients window managers
Message-ID: <17527@pasteur.Berkeley.EDU>
Date: 22 Sep 89 17:14:29 GMT
References: <8909220829.AA00900@korfu.udac.uu.se>
Reply-To: davidh@dent.Berkeley.EDU (David S. Harrison)
Followup-To: comp.windows.x
Distribution: usa
Organization: UC Berkeley Electronics Research Lab
Lines: 20

> Isn't there any (non-standard) way to do this? If not, why is this so?
> Are there any reasons why the user shouldn't give such information to the
> window manager?

Maybe I am missing something here but this doesn't seem to be

1. Have the window manager read a profile.  GWM uses this approach.
   Clients are specified by their class name (the standard
   WM_CLASS property).

2. Have the window manager read specifications from the resource
   database.  Clients can be specified using the same mechanism
   given above.

I suspect the second approach is more general and avoids creating
yet another startup file.

			David Harrison
			UC Berkeley Electronics Research Lab
			(davidh@ic.Berkeley.EDU, ...!ucbvax!ucbcad!davidh)