eOn 17 Nov 2002 10:15:36 +0100, Olivier Chapuis wrote:
>
> On Sat, Nov 16, 2002 at 01:42:12PM +0000, Mikhael Goikhman wrote:
> > On 16 Nov 2002 10:22:53 +0100, Olivier Chapuis wrote:
> > >
> > > 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?
> >
> > I did not immediatelly understand what alpha is good for. But I think I
> > understand it. Any new Add*Style adds a colorset layer.
> >
> > The initial starting background may be a solid bg from "Style Colorset".
> > But this is not very good for defining transparent titles/buttons/borders.
>
> Why? Any way Transparent will be not supported for title bar's.
I thought Transparent may be supported too. If only RootTransparent is
supported, it's not very important whether to have a solid bg base or not.
> RootTransprent will work.
>
> Colorset 1 bg blue, fg white, RootTransparent
> Style * Colorset 1
> TitleStyle Inactive Colorset 1 30
>
> will give a blue inactive title bar "textured" with the root background.
>
> Colorset 1 bg blue, fg white, RootTransparent
> Style * Colorset 1
> TitleStyle Inactive Colorset 1
>
> will give a root transparent title bar.
>
> > I think it is acceptable, instead, to say that the first colorset should
> > be fully destructive, i.e. its alpha is discarded.
>
> I think that this will add unnecessary complication in the code.
> Moreover these "Style Colorset" (and "Style Color") will be used
> for the fg/text and relief. This is a bit problematic ...
It is not very clean that both "Style Colorset" and TitleStyle colorsets
are used (and different colorset properties are ignored). On the other
hand maybe having an external base simplifies TitleStyle, I don't know.
> > Similarly MultiColorset may be destructive, i.e. no alpha in the mandatory
> > Main/LeftMain/RightMain. Other MultiColorset parts may have alpha relative
> > to Main. There are also stretch arguments.
>
> In fact I do not see why we should have any mandatory "type" in the
> Multi* option. We have a solid "common" bg from "Style Colorset" and we
> draw over it. I will see.
The problem is that the solid bg base is almost never useful for titlebars
designed using MultiPixmap. Instead, having the Main colorset as the base
for all other parts may be very useful.
I think we agree that the resulting TitleStyle has only one optional
MultiColorset, but several optional Colorset-s, so in AddTitleStyle
MultiColorset and Colorset work differently.
> Yes, stretching maybe problematic. For example "LeftText a_grad_cs".
> Maybe I will add a "width" argument (e.g., 20p). Also, maybe,
> we can add XPixmap and YPixmap Colorset option.
I think we need to rotate a colorset when different titlebar positions are
used (depending on one or another TitleRotatedCW options). So XPixmap and
YPixmap (if I understand them correctly) are not needed, at least now.
I also don't leave the idea to call all "Pixmap" in the user configuration
"Image" one day. :)
> > MultiPixmap may be removed in favor of MultiColorset if this simplifies
> > the code (I think, yes).
>
> I do not know, maybe the two code can be merged.
>
> Suzanne any opinion?
>
> Any way I will first implement Colorset and the MultiPixmap code will
> help a lot for MultiColorset.
>
> > Seems good for me, one should just distinguish between internal alphas in
> > the colorset definition and the external alpha in the colorset usage.
> >
> > We probably should add different settings for different windows later.
> > Similarly to FocusStyle. I.e.: [Add]TitleStyle XTerm <current_parameters>.
> > Then we may remove decors. But this is really not for now.
>
> Maybe this is not so difficult. But what do you do with a window
> named Inactive ?
I would not discuss now backward compatibility issues. But if TitleStyle
is physically (not nessesarily using the syntax) moved to window's Style,
the main non conflicting syntax should be TitleStyle * Inactive <params>.
I don't think this is needed for 2.6, but we will see.
> > As for BorderStyle, I think it is not very simple if you want to get nice
> > results. It may have MultiColorset too with different colorsets for corner
> > (to be mirrored) and horizontal and/or vertical parts (to be mirrored and
> > tiled). This may wait.
>
> Yes why not. Note that there are no AddBorderStyle cmd so no alpha
> here.
>
> > Seems a lot of work. Good luck. :)
>
> Maybe not so lot of work. At least for TitleStyle and ButtonStyle
> Colorset. Updating the Colorset and the RootColorset may lead to some
> complication (do not know yet). The borders code is really clean :o)
TitleStyle/ButtonStyle/BorderStyle were always considered difficult to be
converted to colorsets. If it is not difficult for you, fine. :)
Regards,
Mikhael.
--
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]
