Matthias Melcher wrote:
> On top of that, Fl_Browser would get all the benefits from Fl_Widget,
> including fonts, colors, check boxes, radio boxes, images, tooltips,
> even composited widgets.
>
> Is this a waste for a Browser with 65000 entries? Sure! But is a
> browser with more than a few hundred entries user-friendly?
Sounds good for 1.4..
Does the API stay the same? If so, sounds really good.
If not, maybe leave the old alone and make a new Fl_Widget_Browser?
Then maybe we can really fix things, like maybe use ANSI codes instead
of
@codes or some such. (I added ANSI to Fl_Browser and it works well for
me.
Can change bg and fg colors. Supplied a patch a while ago. Needed it to
do progress bars and per-word coloring)
> Anyway, back to CMake ;-)
Yes, cmake looks cool. I didn't realize how well it worked
across all platforms, even the VS IDE.
I used it to compile on unix too, cause once you run cmake once,
it pretty much breaks the regular unix Makefiles to where running
'configure' doesn't get them to work again, so 'cmake' with the Unix
generator at least gets them working again. (Still puts the test
executables
in a bin directory, but at least that shows it's consistent!)
_______________________________________________
fltk-dev mailing list
[email protected]
http://lists.easysw.com/mailman/listinfo/fltk-dev
