> FLTK 3.0 with all > features needed for a future GUI library. Compatibility layers for FLTK2 > and FLTK1 would be designed in from the start, so that existing apps can > be converted without much trouble.
I think compatibility is most important! Look at fltk links-page and think of all devolopers using fltk - there is a lot of code existing and this is an important benefit of fltk. Another advantage is debugging status of FLTK 1.8 - why repeating all this mess? I don't know advantages and features of fltk2 (beside UTF-8 ;o), but is there something really so important, making it necessary to throw away all this labour done and make all those people fingering their code? What's about keeping the interfaces and enlarging 1.8 step by step? Adding only one specific feature or modification after the other focuses work of developers, offers a good way to track problems and the community can use benefits at once and look for bugs. The binary interface is not so important to me, only the code must compile with less changes (like inserting namespaces or librarys). _______________________________________________ fltk mailing list [email protected] http://lists.easysw.com/mailman/listinfo/fltk
