On 08/26/2011 09:05 AM, Matthias Melcher wrote: > > Hi guys, > > OK, I think I moved and renamed everything as planned. So at this point, feel > free to participate, add, remove, change as you like. If anyone has code that > can act as a frontend to command line tools, and that can handle stdin, > stdout, stderr, and signals simultaneously, please send code ;-). I need some > kind of simple FLTK text terminal. > > My plans are this: > > - introduce Styles from FLTK2: if used, styles reduce the memory footprint > of every widget by many bytes. They also help to make an app look more > consistent. Very nice. This will also require changes in Fluid.
As opposed to the approach used in FLTK2, I would expand the style object as much as necessary so that all the values that are different in the fltk1.3 base classes have their own entries in the style. Then there can be exactly one default style structure, rather than one for buttons and one for text editing and one for menus. For instance there can be a "button color" and a "text field color". Toward the end FLTK2 was going in this direction but there still had to be 2 or 3 base style instances, and some FLTK1 compatibility was removed to reduce it that much. Adding more box type entries would help. Does your GTK+ style actually load and use the GTK drawing widgets? _______________________________________________ fltk-dev mailing list [email protected] http://lists.easysw.com/mailman/listinfo/fltk-dev
