|
From: Olivier C. <oli...@fr...> - 2000-07-30 10:33:59
|
Mikhael Goikhman wrote: > > On 29 Jul 2000 23:53:36 +0200, Olivier Chapuis wrote: > > > > > I think they all belong to styles@. Or styles-standard@, > > > > but there are also Modules command. > > > > > but probably > > > we don't really need a new component for this. How about adding > > > Colorset config commands for other modules? They also always the same. > > > > Not "in general". Modules themes designer can do what he wants with > > the colors that colors@ provide to it. The spec is just some suggestion? > > Moreover, we cannot do that for Buttons in the view of the number of alises. > > modules@ follows styles@ anyway, because of default module styles. > In styles@ there are only standard defaults for module colorset numbers. > If a theme designer wants to change them, he still can do it in modules@. > Ok, but how we destroy the modules config? In general, we destroy the modules config before we configure a module and also when we leave a modules theme. It seems difficult to change that. So I suggest to do not move colorset "modules themes" modules config. On the other hands we can move the fixed part of the colors config (section IV of the spec) in style@ but we do not win a lot since we probably need to relaod style@ each time we do a modules@ switch. Since it is not a very good idea to move this fixed part into fvwm-themes-config.in we can introduce a new special component called "fixed" where we can put all the config command that have to be read only one time? An other possibilty is to do so that modules@ does not "needs" style@: I do not think that we have to provide styles for the "modules themes" modules in style@ this is the task of modules@. In this case moving section IV into styles@ seems ok. Regards, Olivier |