Matthias: >Yes. I identified a few module types: > - input devices (mouse, keyboard, pen, tablet, etc.) > * WIN32: base library, Tablet support, Pen Computer support > * X11: base libraries and possible extensions > * ...
> - raw drawing (pixel, colors, fonts, shapes, bitmaps, clipping) > * WIN32 api, DirectX, OpenGL, FrameBuffer, SDL, Cairo, etc. > * but also texture memory, bitmaps, printers > - windowing (windows, fullscreen, decorations, system menus, icons) > * WIN32, X11 WM's > * maybe even an implementation on top of "raw drawing", so FLTK > can be its own window manager on simple devices > - OS support > * timer, simple threading and locking > - image format support (already there, but ability to link in more > dynamically) > - communications (optional) > * serial line, TCP/IP, etc. This list is very close to what we have so far ;-) Matthias: > But maybe I am just overshooting the goal ;-) Actually... I think you are hitting the nail right on the head. If we are going to put forth the time and effort required to do this work, I think we should try to make it as robust and flexible as possible. We may not have all of the devices at first, but we should end up with a nice framework for adding them. Thanks, Gerry _______________________________________________ fltk-dev mailing list [email protected] http://lists.easysw.com/mailman/listinfo/fltk-dev
