On 05.04.2010, at 21:18, Greg Ercolano wrote: > I hated to bring it up, as you seem to have the creative inspiration > to do this amazing fltk3 convergence that may 'save' fltk2, and I don't > think we should stop you! > > But the rest of us should probably get focused on closing up fltk1.3 > (as I see you've been doing zipping through the STR's -- thanks! > Looks like I'm a culprit that's got a few open STRs assigned to me > that I should close up) > > There's unfortunately I think loose ends in many of the things we > overhauled in 1.3 (like doxygen) and I'm not sure if we got all the ABI > stuff implemented yet (which we can really only do in 1.3.0), and some > of those other odd things left in the STRs.
Actually, we should all do our best to get 1.3.0 into the world. It's a great piece of software! My FLTK3 approach has proven to work, that's great, really great! But the actual conversion has to be (at least semi-) automatic. What I will probably do is port essential FLTK2 features slowly over to FLKT 1.3, create a wrapper for testing for FLTK 2 to FLTK 1.3, and then translate FLTK 1.3 (and the wrapper) automatically into FLTK 3. It's merely a (huge) search and replace job. We have plenty of time before that to discuss the final naming of namespaces, classes, and functions. Little extra advantage: the automatic translation program should work just as well on other existing source code ;-) . - Matthias _______________________________________________ fltk-dev mailing list [email protected] http://lists.easysw.com/mailman/listinfo/fltk-dev
