> Cairo support on 1 was quite limited. On 2 it was better, but never > complete IIRC. Sinc 1.3/3.0 we have a driver system for rendering which > means that any frontend can be added to FLTK in a somewhat ordeely > fashion. I suggest to add Cairo support as an optional library. This > allows for the end user to decide if he wants Cairo or not for any > available FLTK app.
In any case, we want to get J.Liles Cairo stuff captured - maybe not in fltk-1.3, but feeding into 3.x I guess, along with the fltk-2 Cairo stuff. The Cairo stuff in 1.x is of very limited scope, so possibly not that useful to preserve... SELEX Galileo Ltd Registered Office: Sigma House, Christopher Martin Road, Basildon, Essex SS14 3EL A company registered in England & Wales. Company no. 02426132 ******************************************************************** This email and any attachments are confidential to the intended recipient and may also be privileged. If you are not the intended recipient please delete it from your system and notify the sender. You should not copy it or use it for any purpose nor disclose or distribute its contents to any other person. ******************************************************************** _______________________________________________ fltk-dev mailing list [email protected] http://lists.easysw.com/mailman/listinfo/fltk-dev
