> I'd certainly be interested, it seems! > > Choosing to pull in Cairo at configure probably forces a lot of other > options on the user too - e.g. on Linux they probably have to pull in > XFT and fontconfig too, on OSX they'd be forced to use Quartz rather > than QD, etc... Good point, that's why these limitation should be clearly stated and documented from the start so that we won't go in many trouble in the STR area...
> However, if it could be made to work in a fairly transparent way to the end > user, something like Fl_Gl_Window, ./.. > Ian A wrapper would be easy to do, However, the transparency would be limited to the Fl_Cairo_Window management, not its contents that would contains (like for GL) many non transparent cairo code ... IMHO, we don't want to mess the existing fltk drawing code with cairo as in FLTK2 because it would slow down considerably the lib. Fabien _______________________________________________ fltk mailing list [email protected] http://lists.easysw.com/mailman/listinfo/fltk
