On Wed, Nov 20, 2002 at 06:08:44PM +0100, Dominik Vogt wrote: > On Wed, Nov 20, 2002 at 05:13:46PM +0100, Olivier Chapuis wrote: > > On Tue, Nov 19, 2002 at 11:40:07AM +0100, Dominik Vogt wrote: > > > On Mon, Nov 18, 2002 at 10:14:05PM +0100, Olivier Chapuis wrote: > > > > On Mon, Nov 18, 2002 at 10:40:55AM +0100, Dominik Vogt wrote: > > > > > > > > > > Well, I won't stop you doing it, but are you all aware that the > > > > > whole code is going to be thrown away, probably next year? As I > > > > > said before, I think no new functionality should be added to the > > > > > {Button,Title,Border}Stlye commands anymore. My estimation is > > > > > that at least 50% of the code doing this will be just thrown away > > > > > and on the other hand makes the big decoration rewrite much more > > > > > complicated. > > > > > > > > :o) > > > > > > > > I do not want to wait 3 years or more before to see colorset in > > > > TitleStyle for a stable release. > > > > > > We already have a Colorset and a HilightColorset style. I won't > > > say anything against using more parts of the colour set in the > > > window decorations. But why does it have to be in the BuggyStyle > > > commands? > > > > Because replacement for {Button,Title,Border}Stlye commands will lead > > to interminable discussion which will end after the feature freeze. > > I think this is in the 3.0 todo. Moreover, {Button,Title,Border}Style > > are widely used > > > Style * HilightColorset > > Okay, that won't give us the MultiColorset things, but I don't > think they are this important for 2.6. The advantage is that we > can keep the code unmodified in 3.0. >
You lost other features vs the {Toggeled}{Active,Inactive}{Up,Down} state and Buttons "bg". (Also you will be not able to get a gradient textured with the root background :o) An other risk is that user will style use {Button,Title,Border}Style and do not switch to Colorset config (MultiPixmap). On the other hand, I am agree that using Style {Hilight}{Border}Colorset have some advantages. At present time I've implemented Colorset title bar's with {Button,Title,Border}Style. I may change this. Mikhael an opinion? One point is: TitleStyle blabla Colorset 2 ButtonStyle all blabla -- UseTitleStyle Colorset 2 a Hgradient if we follow the current TitleStyle heuristic this is equivalent to TitleStyle blabla Colorset 2 ButtonStyle blabla Colorset 2 which is totally stupid. What I've done is with TitleStyle blabla Colorset 2 ButtonStyle all blabla -- UseTitleStyle the gradient is applied/computed to/for the full window bar (title & buttons). Similary with BorderStyle blabla Colorset 2 TitleStyle blabla -- UseBorderStyle ButtonStyle all blabla -- UseBorderStyle the gradient is applied/computed to/for the full window frame. Moreover, BorderStyle blabla Colorset 2 is, in any case, applied/computed to/for the full window frame. IMO this is the resonable way to set the border with a colorset. So, {Hilight}{Border}Colorset will be more natural but will depends on some {Button,Title,Border}Style ... > [snip] > > > > Well, if we don't stop adding things, we won't have 2.6 anytime > > > soon. Remember that 2.6 was planned as a quick follow-up to 2.4 > > > to add some nifty functionality before the big clean up. > > > > I was not aware of this. They were very few discussion on the goal > > of 2.6. > > Well, I know most of the time it is that I just make the > decisions, chiefly because we lose interest in the discussions and > nobody cares too much about the outcome. But I really think it > would be good to communicate more about strategy. Agree. I think I/we have time problems. 3.0 will be a good occasion. > We (you, me and > Mikhael) seem to have orthogonal goals in many aspects. > And IMO this is not a bad thing. > > > In my eyes, adding the "Style by Id" thing would delay the next > > > stable release by at least a year. > > > > Or you sure that this will be so difficult. I do not ask for > > conditional style. > > Yes, absolutely sure. It is very disruptive and requires a full > fledged rewrite of the style code - unless we hack up some > temporary syntax that is dumped in 3.0. > Really, I will be very very happy to see Style by Id in 2.6. I vote fort he "temporary syntax", but you decide on this point. Olivier -- Visit the official FVWM web page at <URL:http://www.fvwm.org/>. To unsubscribe from the list, send "unsubscribe fvwm-workers" in the body of a message to [EMAIL PROTECTED] To report problems, send mail to [EMAIL PROTECTED]