> > Now comes the fun part: we will create a compatibility layer for FLTK 2 as > well. FLTK 2 has some great features that were never backported to FLTK 1. > Well, now is the time to put them into FLTK 3! This will make FLTK as stable > as possible while combining all the advantages of 1 and 2. >
Is a FLTK 2 compatibility layer really necessary? FLTK 2 never reached a release version, so I wouldn't expect much demand for a compatibility layer. With all this comes a "code injection system" that makes it possible to > interface FLTK 3 with any other language out there, including overriding > existing virtual functions at run-time, like "draw()", and all the other > FLTK features. > The core application behind this being a skinning system, yes? _______________________________________________ fltk mailing list [email protected] http://lists.easysw.com/mailman/listinfo/fltk
