On Mon, Apr 08, 2002 at 10:52:21AM +0200, Dominik Vogt wrote:
> 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.
>
Yep, but so the F is not really needed? So I think that:
PictureCommon (the depth, visual, ..., the FvwmPicture structure, path stuff,
it is at present time InitPicture)
Picture (elementary FvwmPicture manimulation)
PictureImageLoader (image loading, at the present time FImageLoader)
PictureGraphics (rendering Picture or set of Pixmaps: a set of warpers
for XCopyArea, XFillRectangle and XRenderComposite;
on my machine only :o),
or the same with a F as prefix?
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]
