BTW, regarding this..
From an 'avoiding bloat' point of view, does it make sense
to put potentially large widgets like Trees and Tables into
a separate .lib file, similar to our opengl and image libs?
Since FLTK's mandate is to keep tiny apps tiny, even if
statically linked, maybe there's a benefit to have big widgets
in a separate lib, so that libfltk.a remains "small".
However, maybe it's not worth the trouble, as the computing bar
has creeped up over the years such that these widgets are considered
'minimal'. Even cell phones have pretty complex stuff now.
> > Which tree widget is being targeted for the core library?
> >
> > Which release of FLTK 1.x will be including table and tree
> > widgets into the core? (1.4? 1.3.x, where x>0?)
>
> Originally, I planned to clean the API, add UTF8, the Fl_Table, and a
> Tree widget and be done with 1.3.0. [..]
>
> Anyway, we had'nt decided on a tree widget yet. [..]
_______________________________________________
fltk mailing list
[email protected]
http://lists.easysw.com/mailman/listinfo/fltk
