DO NOT REPLY TO THIS MESSAGE. INSTEAD, POST ANY RESPONSES TO THE LINK BELOW.
[STR New] Link: http://www.fltk.org/str.php?L2504 Version: 1.3-current Cairo in FLTK 1.3 can be seen similar to OpenGL. It merely gives you a drawing canvas. The problem though is, if you link it dynamically, all target machines must have Cairo installed. FLTK 2 is a different story. Here, the developers tried to replace all graphics calls with Cairo calls. IIRC it was never fully implemented when it became clear that Cairo was not fast enough (at that time). A third use for Cairo was Printing Support. However this was solved differently in the end on all platforms and for both FLTK branches. IMHO we should move all Cairo support into a separate library. Just like fltk_gl, we can have fltk-cairo, and just as fltk_gl, it is completely optional. It could still get its own Fl_Driver (just like OpenGL will), so if it is linked, a developer can decide to do all or part of his UI in a Cairo window. But that change would further delay RC3! Link: http://www.fltk.org/str.php?L2504 Version: 1.3-current _______________________________________________ fltk-bugs mailing list [email protected] http://lists.easysw.com/mailman/listinfo/fltk-bugs
