My thoughts - if we are to do this, a thing that might be useful to start with is to go through the fltk2 code and toss out all the specialist widgets that people have added over the years to scratch their own particular itch... Most of them (all of them?) could be just as well done in an add on library, so "polluting" the core lib with these seems wasteful. I would suggest we identify a core set that maps comfortably between 1.3 and 2.x, and port that. Then, if we can be bothered, we can port the other fancy widgets later - or put them into a supporting lib, a la fltk_images...
> I know this has been discussed in the past but, in my opinion, I don't > understand what is the value of creating a new version (fltk3) if we > don't have neither fltk1.3 nor fltk2 stable. Indeed, and it would be nice to have a stable 1.3 as a stop gap until the new work is ready for use. I honestly don't know if we can ever get to a stable fltk2 now... _______________________________________________ fltk mailing list [email protected] http://lists.easysw.com/mailman/listinfo/fltk
