FLTK developers, First I want to thank all of you for all the hard work and effort you have put into FLTK! I really appreciate it.
I started using FLTK back in 2003 or so. I started using FLTK 2.0 because I liked the fltk namespace (feels cleaner to me than FL_ prefixes on everything), and I wanted the very useful tree browser widget. However, OSX compatibility (and other issues) forced me to go back to FLTK 1.1, using FLU for the tree browser. I wrote my code to work with either FLTK 1 or FLTK 2 and maintained it that way for a while, using a simple wrapper so I could keep fltk2 syntax and have a minimum number of #ifdef checks. (Now I doubt I could compile it with FLTK2.) I plan to port my program to FLTK 1.3 at some point in order to take advantage of the new 1.3 tree browser. What I would like to see as a developer is an API that is like 2.0 (namespaces, relative window/widget coordinates, tree browser, etc.) with a compatibility layer for 1.3 applications. Pick the best parts from 2.0, and take everything else from 1.3. Fastest and lightest will come from targeting new applications to 3.0 while compiling is still available for 1.3 applications. Applications can take advantage of new fltk3 features while maintaining backward compatibility. Eric _______________________________________________ fltk mailing list [email protected] http://lists.easysw.com/mailman/listinfo/fltk
