On Fri, Jan 03, 2003 at 08:22:57PM +0000, Mikhael Goikhman wrote:
> The current colorset functionality is simply amazing, but I feel that
> something is not complete. I am trying to see what.
>
> 1) Colorsets in menus.
>
> We still don't have full ActiveColorset support including images or
> gradients. And it would be nice to support Transparent in it similarly to
> FvwmIconMan and FvwmButtons. I.e. it is possible to get active item
> background by just tinting the normal background (a part of a big image).
>
> Greyed items in menus may support the same things using transparent or
> even non transparent GreyedColorset. It is ok with me if the
> compatibility is broken and it should be marked Transparent to have what
> we currently have. Unless there are technical problems to achieve this.
> BTW, GreyedColorset seems to be broken in cvs.
>
I do not think this is difficult to implement. Only the fg colour
from the GreyedColorset is used for inactive items and the full
GreyedColorset is used for the active one.
> 2) Colorsets in window decorations.
>
> I see small advantages in how windows ignore most of the things defined in
> Colorset/HighlighColorset and use TitleStyle Colorset as filters for
> different title states. But I think it will not be very inconsistent to
> fully apply Colorset/HighlighColorset (not just fg/bg) and start
> TitleStyle Colorset from non plain colorset. This way some titlebar
> designs would not need TitleStyle at all, this includes half of the
> current fvwm-themes themes. Of course this is not trivial, since it
> involves the issues like different states and UseTitleStyle, but I hope it
> is solvable. I think it is good to support Colorset/HighlighColorset
> fully. If we do this, Main from MultiPixmap probably may be removed as
> redundant (and I don't worry that this means a design with MultiPixmap
> can't be done without colorsets). I think it also may mean that it is
> possible to use Transparent and not just RootTransparent in Style
> Colorset, but this is not really important.
>
> Similarly to BorderStyle vus BorderColorset.
>
For me all these are post 2.6.
> 3) Root Transparency.
>
> It would be very useful to have the following functionality in fvwm-root
> using "-d -r" or similar option. Read the current random root background,
> (re)create an image from it and then retain it. I hope this does not sound
> meaningless. This way anyone who wants to use RootTransparent should run
> one command and it would work regardless of the current background.
>
This is not possible in general. Why not just use fvwm-root to set
the root window bg? We may add jpg (and svg) support in the future.
> 4) In FvwmPager it would be nice to have {Hilight}TitleColorset, the
> current plain rectangle taken from HilightColorset is really not enough.
>
Yes, this will be good. I do not know if I will have the time to
implement this. My Pager plan is to add
WindowActionFixed (Mouse x) Action
causes the pager to execute Action when you click on a
mini-window and this click does not imply a desk or viewport
change
WindowAction (Mouse x) Action
causes the pager to execute Action when you click on a
mini-window
> 5) Colorset HueRotation (recoloring). Should be more useful that Tint in
> some situations. Would be nice to have.
>
What is the formula? I do not think that this is essential.
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]
