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.
> 2 - When I split Picture into Picture and InitPicture I was not very
> inspired for the name of "InitPicture" and I have still no good idea.
> InitPicture contains the visual stuff init (Pvisual, Pdepth, Pcmap)
> and the image path stuff and the fvwm Picture structure (as picture
> contains picture manipulation). Any suggestions for a better
> name for InitPicture?
Name it after its externs, PPicture.c.
> 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.
--
Dan Espen E-mail: [EMAIL PROTECTED]
444 Hoes Lane Room RRC 1C-214 Phone: (732) 699-5570
Piscataway, NJ 08854
--
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]
