On Sun, Apr 07, 2002 at 04:45:16PM -0400, Dan Espen wrote:
> Olivier Chapuis <[EMAIL PROTECTED]> writes:
> > Hello,
> >
> > I've a few (re)naming problems.
>
> Opinions follow.
>
> > 1 - As fvwm, XRender use Picture as its main "picture" structure.
> > This is currently solved by the following lines in Fft.h
> >
> > #ifdef HAVE_XFT
> > #define Picture XRenderPicture
> > #include <X11/Xft/Xft.h>
> > #undef Picture
> > #define Picture Picture
> > #endif
> >
> > Not terrible ... specially if we use XRender for alpha rendering.
> > So I suggest to rename the fvwm Picture structure by FvwmPicture.
> > And so also rename libs/Picture.{c,h}: FvwmPicture.{c,h} or
> > FPicture.{c,h}. Any better idea?
>
> FPicture.{c,h} is good.
The original idea was to replace the 'X' with an 'F' where
appropriate (Xft -> Fft, XShape -> FShape). If there is no chance
that we need FPicture for something different the name is good.
> > 3 - Now that xpmroot support PNG (and XBM) should we rename it (with a
> > symbolic link from xpmroot to the new name)? If yes one may think
> > that fvwm-root is a good name, but I do not think so because in fvwm
> > "-" separated names are scripts. FvwmRoot is obviously bad, but what
> > about "fvwmroot" ?
>
> fvwm-root, I don't see why the fvwm- rule can't be used for binaries.
I agree. Especially since there's some other tool named xpmroot
on the net.
Bye
Dominik ^_^ ^_^
--
Dominik Vogt, email: [EMAIL PROTECTED]
LifeBits Aktiengesellschaft, Albrechtstr. 9, D-72072 Tuebingen
fon: ++49 (0) 7071/7965-0, fax: ++49 (0) 7071/7965-20
--
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]
