Gerry Weaver wrote: > Matthias: > >> FLA_, Fast Light Abstraction (layer) sounds OK to me. > > It seems like fla_/FLA_ is the current favorite. Anyone else?
okay for me, sounds good. > Matthias: > >> I mentioned it before: it would really be nice to be able to use two >> rendering HAL's at once. ... > > So... in other words, FLTK would be rendering to multiple FLA backends > simultaneously? Simultaneously? Not concurrent, but interchanging. Think of fl_begin_offscreen() and fl_end_offscreen() [IIRC] as a way to switch the drawing context from one device to another. Similarly for printing (in Windows you would switch the DC, et voilà ;-) ). In cairo there is a similar option to switch to another "device", e.g. to a pdf device. This would seem to imply multiple levels of FLA backends. What I mean is, a platform based FLA backend would represent everything but the drawing or graphics, which would be a separate proposition. For example, you would have libfla_x11/libfla_unix or libfla_gdi/libfla_win32. The libfla_x11 would be dedicated to drawing/graphics where as libfla_unix would include all of the other platform specific code. I guess there would be a wrapper level call to select the graphics output backends/devices? This is an interesting idea. It would be similar to the output device concept Roman had mentioned earlier. Yes, that's something that would make life much easier. Having something like an opaque "handle" to a device context, and then calling the normal drawing functions ... > > Note: I understand the monolithic lib build requirement. It's just easier for > me to visualize the code structure when I think in terms of separate libs. AFAICS, this wouldn't contradict. Albrecht _______________________________________________ fltk-dev mailing list [email protected] http://lists.easysw.com/mailman/listinfo/fltk-dev
