In message <3.0.3.32.19971208204710.007c9650_at_jcwells.deskmail.washington.edu>
jcwells_at_u.washington.edu (> ) writes:
> Having been a X user at the local university I never knew how much actually
> went into creating a _good_ interface. Now that I am writing my own
> interface I see that there is much work to do to get it right.
>
> Many interface options that can be set in X can also be set in fvwm2. I
> will give an example for the sake of discussion. For example: the
> sample.fvwm2rc file has an init function to perform a root window change.
> This same behavior can be accomplished via .xsession.
>
> I do foresee a couple issues.
[ snip ]
And then some.
The configuration of an X workstation is a problem that needs addressing.
I don't think things like CDE have really solved them. Rather, some way
of managing it without depending on a limited-configure setup like CDE is
needed.
It is relatively easy to write a program to manage any one individual
file. But across multiple files, most of which are totally different from
each other, it is much harder.
Still, I wish something like that existed... maybe something of a
theme-editor for X that understand the differenent files and how they
related. I have seen anything written about this in any kind of serious
detail.
--
Visit the official FVWM web page at <URL:http://www.hpc.uh.edu/fvwm/>.
To unsubscribe from the list, send "unsubscribe fvwm" in the body of a
message to majordomo_at_hpc.uh.edu.
To report problems, send mail to fvwm-owner_at_hpc.uh.edu.
Received on Mon Dec 08 1997 - 15:03:36 GMT