as i am reading through the cairo discussion thread (an taht is quite along one, espexially when you read it in the browser on a phone - hence the typos) it feels like we have to rethink some of the rendering and compositing.
Bill mentio.ed that some engines reneder into RAM and copy a single rectangle to the screen. Also, converting everything to ARGB internally seems like a good idea. Future 'beautiful' widgets will likly be drawn with scaled images instead of lines anyway, so FLTK compositing should be really fast doing that. Transparency also plays a huge role here. So: O. Fast bitmap handling O. Compositing in RAM O. Must still run on embedded systems O. Support for multiple 'surfaces' like Cairo and OpenGL Suggestion: O. Current interface using drivers is already good O. Improve bitmap capabilities O. Improve offscreen rendering O. Seperatedrivers into their own modules O. Add minimal driver that can be used as a base for all other implemetations (i can do that) O. Add Cairo driver and OpenGL driver _______________________________________________ fltk-dev mailing list [email protected] http://lists.easysw.com/mailman/listinfo/fltk-dev
