> > > I'd thought maybe: > > > > > > 4. Produce a "1.2" based on 1.1.8 with UTF and printing... > > > > So that would be a temporary 1 aiming at 2 ;-)
5. Start 'new' 2.0 with 1.1.x base and move current one in fltk-nuke branch. I was assuming this will be discussed on dev. group :) I am really glad Matt initiated this discussion since it was really needed. As Michael, Mathias, Greg and others noted, there are bunch of applications with varying range of complexity based on 1.1.x code. Even if is prevailed that 2.0 is now official next version, it is impossible to create 'compatible' layer; code is too much different. From this solution only freshly started projects will benefit, others will have to use either old version or maintain their own branch. IMHO 2.0 was dead end when namespaces introduced; even when gtk guys brougth gtk2, they carefully planned to not break every possible thing. Also when Qt (after all this years) pull out a new version, breakages are small; base stuff are mostly intact. Hell, even current 1.1.x code can be much easier ported to efltk than to current 2.0. Yes, with above statement I am going against my goals of pushing 2.0 forward, but working on something 'that-will-break-over-the-night' really makes me pi**** off (and others too). When Mike added note for possible release manager, at first I was going to step in, but after efltk expirience (maintaining EDE code with full gui library is not the easiest thing), I will shamelessly step out. And what is my proposal was about? Create 1.2.x with UTF-8 support and based on that build 2.0 (or directly jump to 2.0 number). AFAIK there is code Roman worked on (printing support) which will be much easier to integrate into 1.1.x based code than current 2.0. Also current unfamous Image api (or parts of it) is a good candidate for backporting too. Others ? > 1. continue separate development of FLTK1 and FLTK2 Stronly against this. It is much better to focus all manpower to one than to split between them. With this, release cycle will be much faster. -- Sanel _______________________________________________ fltk mailing list [email protected] http://lists.easysw.com/mailman/listinfo/fltk
