On 16.09.2008, at 11:21, Fabien Costantini wrote: > Replying to myself: >> 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. > Last but not least, as it has been discussed, it would be a *hell* > to adapt cairo code to fltk drawing code and maybe not completely > feasible...
Who can architect this? What we would need IMHO is hand full of virtual classe to create a low level interface between FLTK and the OS libraries. On the one end, FLTK can be modified and extended without any machine considerartions, and on the other end of those (four or so) classes would the hardware/ OS interface live. If that interface is complete and well defined, optionally pluggable, we can support Cairo relatively easily. If compatibility is a concern, an App can be started with the X11 backend. If antialiasing is needed, Cairo is the backend of choice, and for speed OpenGL would be a nice base for a GUI. We would gain framebuffer support as a side effect. The minimum hardware layer for FLTK is coloring of a pixel, a timer, and a mouse or touch event. If we can reduce the interface to that level, we can build up from it and provide a GUI to pretty much anything that has pixels. Matthias ---- http://robowerk.com/ _______________________________________________ fltk mailing list [email protected] http://lists.easysw.com/mailman/listinfo/fltk
