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:
> > On Sat, Nov 16, 2002 at 10:22:53AM +0100, Olivier Chapuis wrote:
> > > Hello,
> > > 
> > > I would like to implement Colorset in title bar's. I would
> > > like to implement MultiColorset too.
> > > 
> > > Is this reasonable:
> > > 
> > > Add:
> > >   
> > >   Colorset cset [alpha]
> > > 
> > > to the {Add}TitleStyle, {Add}ButtonStyle and BorderStyle
> > > command. These commands will apply the colorset cset background
> > > on the Title bar, button bar and border with the given alpha.
> > > 
> > > Add:
> > > 
> > >   MultiColorset \
> > >           Main cset [alpha] \
> > >           LeftMain cset [alha]
> > >           ... etc ... as MultiPixmap
> > > 
> > > to TitleStyle.
> > > 
> > > Any comments?
> > 
> > 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?

> I do not believe on estimation about
> fvwm code, I believe on written code (or on code that are going to be
> written). At least 3 times "conditional style" stop me to implement
> some stuff. Now I see that conditional style will not be in 2.6 (fine)
> and that we do not have even style by Id (which is IMO a must for
> 2.6).

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.

> Moreover, I do not see the problem with the {Button,Title,Border}Style
> commands. There are dramatically powerful (yes there are some odd
> things, there are missing feature and yes I will add maybe some).

They are also horribly inflexible (all configs are global), buggy
(leaking memory) and unintuitive (*weird* syntax).

> The
> only real pb I see is that they are not fvwm Style and this pbs is not
> really a drawing pbs.
> 
> BTW, here my 2.6 todo list (optimistic).
> 
> - Colorset in {Button,Title,Border}Style
> - A type of "gettext" support in config file
> - Better key/mouse binding in the Pager
> - minimal randr support (XFree-4.3 will have a functional randr for
> resizing and rotation)
> - Style by Id (maybe Dominik)
> - Icon background (maybe Dominik)
> - bug fix, testing, bug fix, testing, bug fix ........

Wow!  I already mentioned that I want to put 2.6 into feature
freeze no later than 31st of December, did I?

My list looks like this:

 - Clean up tear-off menus (a huge task)
 - bug fix, testing, bug fix, testing, bug fix ........

In my eyes, adding the "Style by Id" thing would delay the next
stable release by at least a year.

> I've no 3.0 todo list. I will begin to think to 3.0 when 2.6.?
> will be released :o) 

Bye

Dominik ^_^  ^_^
--
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]

Reply via email to