Thomas Adam wrote: > 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. > > -- Thomas Adam >
I think no one in this world today really uses A) FVWM *and* B) FVWM with its default configuration. I think, because of this, a default configuration is not that important. I think, a better idea could be to leave the default config as minimal as it is, and instead of changing the default config, better invest some time into an idea of offering some example configurations for new FVWM users. The use case is this: A new FVWM user surely has his/her own opinion how FVWM should be configured. No matter how FVWM is configured by default, the users would change it anyway. This is the reason, why they use FVWM, because FVWM can be tailored to become some kind of dream GUI. When a new user runs FVWM for the first time, the FVWM main menu could contain a menu entry that opens a web browser and causes the web browser to load a web page somewhere at "www.fvwm.org". This web page could contain some example configurations, and the user could choose one of them to use it as a starting point of his/her own tailered configuration. The more features you add to the default config, the more possibly unwanted features the user has to switch off. Just my two cents about this... Michael
