> > This overlaps with the Cairo question: X11 is absolutely not reserved to > > Unix. We had a branch for a while that would compile an X11 version on > > OS X so that apps can be run remotely. Also, _APPLE_QD_ vs. > > _APPLE_QUARTZ_ is just a crutch anyways and adding _APPLE_X11_ and > > _APPLE_CAIRO_ would probably be wrong. > > > > Can we somehow split this up into: > > > > FL_OS_WIN32, FL_OS_UNIX, etc. > > > > and > > > > FL_GFX_CAIRO, FL_GFX_X11, FL_GFX_WIN32, FL_GFX_VNC, FL_GFX_QUARTZ, etc. > > > > To be consistent, we would then have to mark the window manager as well, > > I guess: > > > > FL_WM_X11, FL_WM_CARBON, FL_WM_COCOA_, etc. > > The "USE_FOO" defines are already there for some of the drawing > features, why not continue that. > > As for OS-specific stuff, the compilers already define what we need.
I also thought of having another USE_X11 flag for the case where X11 is used independently of the OS. Thinking about it twice, it would indeed be possible to achieve what we want in a better way if we just add for now a USE_X11 flag instead. This way, it will only indicates the graphic layer used is X11 whatever the OS is, and thus ; it would _have_ to precede of test OS'es test cases. This could be a good compromise between Matt view and Mike's one. Albrecht, GFX means Graphics, as opposed to OS'es and Matt point is that in fact we confuse today what is related to the OS from what is related to the Graphics. I agree with that but in the long term as for 1.4 where it would be useful for pluggable layers architecture :-) Fabien _______________________________________________ fltk-dev mailing list [email protected] http://lists.easysw.com/mailman/listinfo/fltk-dev
