Roman Kantor wrote: > Another possibility to generate postscript or pdf through CAIRO as a > backend.
This is a good point actually - Cairo works pretty well for this, I used it to generate PDF output from my music editor program, and that worked very well, and could handle utf8 text (Japanese songs as it happens) quite well. The prototype used cairo for all the rendering, but it was *painfully* slow, so in the end we used fltk native rendering for the on-screen stuff and only used cairo for the PDF output. This meant we kind of had to write everything twice... but one of my colleagues developed a generic wrapper API that used fltk/cario backends that we could switch during runtime and that worked pretty well. And made it easy to do "back to back" comparisons between the cario and fltk rendering. Fltk was quicker, but the cairo does look nice - though on OSX the difference is almost indistinguishable - I guess because the OSX rendering is all anti-aliased anyway. And we only used the "toy" font-handling API, as Roman said. I looked at the "proper" font API in cairo, but it was too complicated for my brain to grok... _______________________________________________ fltk mailing list [email protected] http://lists.easysw.com/mailman/listinfo/fltk
