Thomas Adam <tho...@fvwm.org> writes: > On Mon, Apr 18, 2011 at 12:27:51PM +0100, Thomas Adam wrote: >> Hi all, >> >> This intended to be something fairly long-running, and I personally don't >> wish to make the UI decisions myself, although I will keep a very close eye >> on the FVWM-specific aspects of a proposed config to make sure it's done >> "right". >> >> What do I mean when I say "right"? Well, for far too long now FVWM has had >> a major thorn in its side -- the default config *sucks* to put it bluntly. >> It's been a well known issue for years that it looks like a throwback to >> 1995 [1] and it's time to modernise it a bit. >> >> There was an aborted attempt at this by Nick Fortune and myself [2] which >> you should read before attempting this, as although the thread is a good >> five years old now, the concept in there are not. *Please read it*. >> >> I want a few things from a new config: > > [...] > > Has anyone done any more work on this? I've received nothing off-list to > indicate that's been the case -- and I do not know how, if at all, this is > being coordinated which is slightly annoying.
Remember we couldn't agree on the 1 pixel border? I think that was the end of it. What would you think of a dialog that allowed the user to pick the border width? I think any of us could hack one of those up but it wouldn't be the ultimate solution for me. My clock, biff, and perfmeter must have narrower borders than other windows. So, dialog that lets you set border width with a style option. Only issue there is that it must be able to manage the sequence of generated style commands. Some of us thought that FvwmTheme would be the answer. It got too big for me to consider. I still like my setup which allows for a number of default themes, and does nothing if you don't ask it to. I thought the "clever" part of the approach I used is that each style installs a command that allows you to remove the style. Sort of object oriented in that each style comes with a constructor and destructor. A while back I made some of the default colors blue so there is a difference between 1995 and today. Not a big difference, but it is different. Also we've slightly grown the default config with a menu that can invoke XDG compliant programs. -- Dan Espen
