Me: >> Last year(?), during the discussions about 1.3.x and beyond, >> someone suggested abstracting out a common library of low-level >> functions that would then sit below both FLTK1 and FLTK2. This >> was just to streamline developer effort and reduce the overall >> code base. >> >> It could also be a means to start pulling the two developments >> together over time, ... but as there are only a few active >> developers for FLTK1 and even fewer for FLTK2 it's all a bit >> pie-in-the-sky :-(
Gerry: > I've been thinking this over a bit more. I have a couple of folks > that are c++ programming students. Perhaps I could make use of > them to get something going. I guess there are a couple of different > ways to approach this. One would be to take a similar approach to > FLTK2 (fork and start from a FLTK1 base). The second would be to > develop a c++ api as an optional library leaving the lower level > intact and in c. The latter would probably require a bit more effort > to implement. Would there be any interest in such a beast? The general feeling that I had from the discussions last year in fltk.development, at least among the FLTK1 developers, was that previous code forks, no matter how well intentioned or technically justified, had all run out of steam for one reason or another. It was felt important not to sub-divide development effort again, and to continue to introduce UTF-8 into fltk-1.3.x. This would remove one of the major differences in capability between FLTK1 and FLTK2, and would also bring the fltk-1.2 fork back into the core. Matt provided his vision for how he saw the fltk-1.3.x development proceeding http://www.fltk.org/newsgroups.php?gfltk.general+v:25151 The common low-level library idea was proposed later, but it was clear that the UTF-8 integration should be completed before taking this idea any further. As far as I know, the UTF-8 work is almost complete, but there is still a little tidying up to do to make the interface consistent and obvious, to document properly, and to work through the relevant "1.3" STRs. See http://www.fltk.org/roadmap.php It might be more appropriate to move this to fltk.development where the more active FLTK1 developers might be able to give more feedback. Cheers Duncan _______________________________________________ fltk mailing list [email protected] http://lists.easysw.com/mailman/listinfo/fltk
