On 19 Feb 2012, at 00:42, Bill Spitzak wrote: > I received a direct question from Kristian Høgsberg <k...@bitplanet.net> > as to whether there is any effort to get FLTK running on Wayland? > > As far as I can tell this means drawing everything with Cairo + Pango > into a local memory buffer, and tell Wayland to use that buffer as a > source image. This would require perfect Cairo rendering which would be > useful anyway (I suggest that the default for X be changed to Cairo).
How does that pan out for performance, though? A couple of years back we cobbled together a mechanism that allowed one of our apps to use fltk for the GUI and most of the rendering, but the main view window could be either rendered via fltk or cairo (selection at runtime, we used a layer of thin wrapper functions...) so that we could get full anti-aliaisng and compositing of images across platforms. This was fine, but the cairo mode was painfully slow, so most times we only actually invoked it in the specific case that we were rendering to a PDF surface in the end, for capture of the final output. And on OSX, you couldn't even tell the difference since the base OSX rendering was anti-aliased and composited nicely anyway! Made a big difference on X11, but *really* slow. And the font/text handling with cairo is a pain - fltk font handling is *much* simpler. So, anyway, that mechanism is still in place, and still slow - though still using whatever version of cairo was "current" at the time, we never upgraded once we got something that was stable and working... Maybe newer cairo versions have addressed the performance issues, but if not it is a complete non-starter for a lot of the things I'd want to do. YMMV. How does GL play with Wayland then? I'd want GL. Maybe GL is an option and we can do all of fltk via that (GL) instead of cairo? Anybody know? -- Ian _______________________________________________ fltk-dev mailing list fltk-dev@easysw.com http://lists.easysw.com/mailman/listinfo/fltk-dev
