>> Just curious, what do you do with this obscure FLTK2 fork? > > I've been thinking about making a post on it (FLPTK - Fast Light > Plugin Toolkit - for lack of a better name) for some time now - a > new one, that is; I made one during the early stages of the project > about four years ago: (the list of differences from FLTK2 is outdated) > http://fltk.org/newsgroups.php?gfltk.development+v:3682 > [...]
Looks like this runs almost, but not quite, in parallel with FLTK. FLTK has only needed to consider one thread with Fl::run() in it because that relates to a typical limitation in GUI handling by the common operating systems. However, your addition of a Context class might echo what has been implemented recently for printing support. Maybe there's some common ground. I'm not the best person to comment. > I've also recently - in git repo - ported the UTF-8 API additions > from FLTK1.3 and renamed and refactored some of it to make the API > more consistent and get rid of some TODOs in the code. Do you have a summary of what you did? Could be useful, as FLTK-1.3.x is trying to incorporate and harmonise the old O'ksi'D code from 1.2 and UTF-8 code from 2.0. > Once up to scratch with FLTK2 functionality, perhaps an un-forking of > FLPTK functionality (without compatibility stuff) could take place. > That is, if said functionality is relevant for FLTK. You never know. Matt has been working on a Plugin architecture for 1.3.x, but I don't know whether that would fit your needs, and it may be desirable to have some sort of Context functionality. Only time will tell once we have 1.3.0 out and can look at 3.0 and beyond. D. _______________________________________________ fltk-dev mailing list [email protected] http://lists.easysw.com/mailman/listinfo/fltk-dev
