On 05.04.2010, at 09:17, Duncan Gibson wrote: >> There's a lot of balls in the air right now; 1.1.x has supposedly >> frozen, and 1.3.x is still in dev.. so users will want to know what >> to do if e.g. 1.1.10 won't build on the latest release of linux. >> Their only option it seems would be to move to 1.3.x, but that's not >> complete yet. >> >> Would really like to see focus on completion of 1.3.x, and not get >> too distracted on the long term, as it seems like we're still in a >> transition state at the moment. > > I agree completely. But it's clear that the core team are busy, and > there are a lot of loose ends to be tidied up and checked.
Allright. I checked a few things today and found the following: my current approach for FLTK3 with wrappers for FLTK1 and FLTK2 emulation works for all the cases that I tested. I am quite happy with the approach and I believe that we have a good solution, however... 1: Greg's right. We should finish 1.3 first and release at least 1.3.0 2: the porting is stupid boring manual labour ;-), basically a huge find and replace, which must be fully automatic 3: the FLTK1 wrappers are quite simple and could be semi-automatic 4: the FLTK2 wrappers need full attention by experienced developers, but when implemented will add great features to FLTK3 that FLTK1 users can then use too So let's get 1.3.0 out. - Matthias _______________________________________________ fltk-dev mailing list [email protected] http://lists.easysw.com/mailman/listinfo/fltk-dev
