> Another quite big problem is that it is damn *slow*, think > about renaming the Toolkit FLTK a more adequate name like > SLTK before heavy use.
Yes, I find it slow - that's partly why the code I'm struggling with has the two back-ends. A fltk one for general work, and the Cairo one for when you need a high-quality output. > Instead, we should have provided a very light and simple API > like the code in the cairo demo plus some fltk internals > hacks to support the surfaces. > This way, best of both worlds could be achieved: > Simple rendering made as usual, complex rendering with the > use of cairo. Like GL... One thing I find awkward about Cairo is there seems to be an awful lot of platform specific code needed to get the thing going. Once you have your Cairo context it is not so bad, but there's a fair bit of platform code to get there. That just seems wrong these days. -- Ian SELEX Sensors and Airborne Systems Limited 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 mailing list [email protected] http://lists.easysw.com/mailman/listinfo/fltk
