[as-devel] look and feel (was: 1.8 ?)
Albert Dorofeev (albert@tigr.net)
Wed, 28 Jul 1999 22:13:12 +0200
> > <look>
> > ... Data for appearance.
> > </look>
> > <feel>
> > ... Data for feel.
> > </feel>
>
> A good idea. Difficult to implement, though. Problem is, AfterStep's
> on-the-fly reconfiguration system assumes that reading certain files
> will define certain things. For example, it deletes all MyStyles before
> reading the look file. This idea is currently feasible, if we know in
> advance what tags (<look>, <feel>, etc) will be in the target file.
Don't get me wrong, please, but this single issue is the
most confusing IMHO around AS. I think that all new users
as well as more seasoned ones often confuse looks and feels.
Yourselves are often forced to look into the config files
to figure out where a particular option should go.
Why is there a differentiation between look and feel? No,
I understand the idea but is it really useful? I mean
*really*? Why not merge them into one thing? It would
be much easier to explain and configure.
I suppose there were already wars for the sake of separate
vs. merged looks and feels and I am not attempting to
start a yet another one. It is just that most of the time
this differentiation does not matter and sometimes it
gets in your way even. Perhaps, there should be something
else than look and feel? Maybe, the definitions of keys
and mouse buttons should be the only things that go into
the feel file? Then, at least, you would not get weird
reactions to clicking buttons in the title bar...
Tigr
--
Albert Dorofeev http://www.tigr.net/ http://bewoner.dma.be/Albert/
PGP fingerprint = C9 49 D0 F3 41 FA 8C D8 E9 5C 6A D4 F1 6D 65 15
Anything good in life is either illegal, immoral or fattening.