Quoting Brian Servis (servis_at_purdue.edu):
> *- On 13 Jun, Brian Servis wrote about "FVWM: CLIENT_MACHINE for Style attributes?"
> >
> > Is it possible to use a window's CLIENT_MACHINE for Style attributes.
> > I often have shells opened up on several different hosts, all with their
> > DISPLAY set to my local machine. It would be great to be able to use
> > the StartsOn[Desk|Page] property to constrain the windows from those
> > hosts to certain desktops. This is especially true when I am running
> > the same app on the different hosts and thus the windows all have the
> > same NAME, CLASS and RESOURCE strings.
> >
>
> As I was think about this, I thought about something that could come in
> handy when defining Style attributes. It would great if the Style
> attributes could be defined individually or globally for each of the
> windows NAME, CLASS, RESOURCE and MACHINE strings. What I mean is that
> say I want all windows with a windowname of 'transient' to have NoTitle
> but those same windows from CLIENT_MACHINE='remote' to StartIconic.
> Under the current implementation I don't think this is possible(Correct
> me if I am wrong). So perhaps the windowname could be either a single
> quoted string for the global case or sets of quoted strings(no spaces
> between), one for the windowname and one for the string to match
> against. An example:
>
> # no second quote immediately after the windowname means global
> Style "transient" NoTitle
> # a second quoted pair immediately after the windowname means apply
> # only to the window with client string matching "remote"
> Style "transient""client""remote" StartIconic
> # If there are an even pair then the first of the pair is the string and
> # second is the windowname to match.
> Style "client""remote" StartOnDesk 2
>
> This enhancement, if added, would be backwards compatible since a lack
> of a additional quoted strings would mean apply to all windows matching
> the windowname as is the case now.
AFAIK, this would break the parser. I would prefer a syntax something like
Style "ICON=xclock" StartIconic
Style "TITLE=Netscape:*" StartsOnDesk 26
Style "MACHINE=nsahost" Decor ThoughtPolice
This is similar to what is done by FvwmIconMan, and would resolve a lot of
the ambiguity inherent in the current system. OTOH, given the kind of
complex logic some people seem to want, it might be better to have a
facility to set styles from a module, then you could have a module
programmable to do things like
if (ICON=xclock && MACHINE=sping) Decor AtlanticTime, NoHandles
But perhaps that would be pushing it.
--
Adam Rice -- wysiwyg_at_glympton.airtime.co.uk -- Blackburn, Lancashire, England
--
Visit the official FVWM web page at <URL: http://www.fvwm.org/>.
To unsubscribe from the list, send "unsubscribe fvwm" in the body of a
message to majordomo_at_fvwm.org.
To report problems, send mail to fvwm-owner_at_fvwm.org.
Received on Sun Jun 13 1999 - 17:42:18 BST