FWIW, for future versions, I am much less worried about whether fltk should use STL and C++0x extensions internally (you can of course use any extensions you like in your own code already...)
I am worried about how we embrace the future of GUI design - touchscreens, gestures, multi-touch, etc. That really changes a lot of the things we take for granted about GUI widgets, and has a potentially huge impact on the UI toolkit - i.e. fltk. So for now, let's get 1.3 stable, get fltk3 baselined so we have something to work on, then worry about what we *really* need to fix next. I honestly think touch interaction is a much more significant issue than whether we use STL internally. Disclaimer: My view may be distorted, as we have been developing touch-screen consoles for various systems for years, and are now starting to see features we've struggled with over the years appearing in consumer facing API's. What would we have given to have had the functionality of the iPad API's in our consoles 8 years ago... (Note: that's the functionality of those API's, but not those specific API's per se, many of which, well, not to my taste perhaps...) SELEX Galileo Ltd Registered Office: Sigma House, Christopher Martin Road, Basildon, Essex SS14 3EL A company registered in England & Wales. Company no. 02426132 ******************************************************************** This email and any attachments are confidential to the intended recipient and may also be privileged. If you are not the intended recipient please delete it from your system and notify the sender. You should not copy it or use it for any purpose nor disclose or distribute its contents to any other person. ******************************************************************** _______________________________________________ fltk mailing list [email protected] http://lists.easysw.com/mailman/listinfo/fltk
