On Wed, May 08, 2002 at 10:48:39PM +0000, Mikhael Goikhman wrote:
> On 08 May 2002 07:28:29 +0200, Olivier Chapuis wrote:
> >
> > On Tue, May 07, 2002 at 10:43:08PM +0000, Mikhael Goikhman wrote:
> > > On 07 May 2002 22:22:13 +0200, Olivier Chapuis wrote:
> >
> > Hum, I do not know this CDE stuff. Can you be more precise?
>
> I don't know it either, but I can imagine what it is by looking at xpms.
> CDE xpms use symbolic names, so changing CDE color schemes changes
> symbolic image colors, this way images may include 3d elements using
> shadow/hilight colors.
>
> I did some search and here is some info (the second is in German):
>
> http://www.w3.org/People/danield/xpm_story.html
> http://www.remote.org/sven/CommonDesktopEnvironment_CDE_.html
>
Thanks. As I say in an other message I do not think that this should
go into colorest. It seems that this concerns image loading, but maybe
I am wrong.
> > > > Others ideas:
> > > > - Add an fg_alpha option : with xft rendering we can apply an alpha
> > > > channel to the text. Maybe good for "greyed" menu colorset and buttons
> > > > in IconMan which represent an iconified window.
> > >
> > > I hope I understand it right that fg_alpha is percents, not color.
> >
> > Yes. In fact it seems that we can just allows a percent after the fg
> > color: fg black 60.
>
> Maybe. In any case I think that fg with one argument should reset alpha.
> On the other hand a separate fg-alpha option would allow something like:
>
> SendToModule FvwmPerl eval unlock(); \
> foreach $a (1 .. 100) { command("Colorset 1 fg-alpha $a"); }
>
> :-)
>
with just fg:
SendToModule FvwmPerl eval unlock(); \
foreach $a (1 .. 100) { command("Colorset 1 fg black $a"); }
?
>
> How about this:
>
> *Pixmap foo.xpm # defines destructive background, like now
> Alpha*Pixmap bar.xpm 23 # adds the second image
> Alpha*Pixmap # removes the second image
> *Pixmap foo.xpm # removes the second image as well
>
> png image with alpha channel that is defined in *Pixmap is forced to have
> alpha 100. png image that is defined in "Alpha*Pixmap bar.png" gets its
> alpha. This seems to be well defined. Correct me if I say a nonsense.
>
> Or maybe just use completely new syntax like:
>
> Plain, *Gradient # defines destructive background, like now
> Image [Tiled,Aspect] foo.png # [Bitmap fg bg] may be a parameter too
> AlphaImage [Tiled,Aspect] bar.png 23
> AlphaImage # other names: SecondImage, ExtraImage
>
Both method seems ok. However, 2 pbs come here. Maybe we should
first think how to implement at the config level colorset in
{Title,Button,Border}Style. Is there a consensus about adding
composed pixmap in colorset?
> > > Another idea. There was a request to add shadow to texts, I thought about
> > > a fg_shadow color property of colorsets. Can this feature be handled by
> > > FlocaleDrawString?
> >
> > Yes it can be (and FvwmScript can already do it if I well understand
> > the feature). This needs work however: passing the colorset and take
> > care of the height and width (add 1 pixels).
> > So fg_shadow is not set by default and have a special key word sh
> > to use the sh color and is destructed by fg_shadow without argument
> > (but not by a simple fg ?).
>
> Something tells me that it is not good for colorset to impose presence
> or absence of the text shadow. Also shadow may have a thickness parameter.
>
Yep.
> Maybe it is possible to add text shadow thickness when specifying a font?
> And fgsh option of a colorset used when thickness is not 0. I don't think
> that sh color is a good default for fgsh, I think it may be computed from
> fg by applying shadow function (not from bg), and fg always resets fgsh.
>
Of course sh is not a good default for fgsh ...
So maybe something like Style * Font "relief int:curent_font_desc".
> Finally, Olivier, I really like what you do to improve fvwm.
>
Thanks, 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]
