Shon Pritchett wrote:
> I am a little scared to change APIs at this point but is it fair to say fltk
> 1.3 is the most actively developed right now?
Definitely.
FLTK2.0 has been trying to get to a release state for years, and
I think it's mostly stalled.. still in dev, and AFAIK no release date
in sight.
There are a few reasons for the stall, I think. Here's one that probably
hasn't been mentioned.
I might be wrong about the history, but I think Bill Spitzak, the
original
developer of FLTK, started the FLTK 2.x trunk to do a "cleanup" of the
API,
and several FLTK developers joined on that project. But it stalled,
I think partly because the commercial software Bill is a lead
programmer on,
and needed FLTK 2 for, Nuke, (which is the software that really got FLTK
rolling in the first place) switched from FLTK to QT (IIRC) for internal
reasons to do with the company that owns Nuke, and thus Bill had to
switch
gears in his day job. So I think the 2.x port lost some inertia there
when
the lead guy couldn't justify driving it anymore.
Also, the 2.x rewrite and fixes proved to be a big thing to do, and it
missed many of its release dates, so many folks decided to stick with
1.x.
And since there's a decade of FLTK 1.x apps that people are maintaining,
there's a strong force driving its continued development.
1.3.x is the active development, and is going to be the way to go
for the foreseeable future. 1.1.9 is the current stable release.
1.3.x is not different from 1.1.x API-wise; 1.3.x is mainly a bump
in the major version number because of the UTF8 additions which changes
a lot of stuff under the hood. But most old apps will still compile fine
under 1.3.x unchanged.
_______________________________________________
fltk mailing list
[email protected]
http://lists.easysw.com/mailman/listinfo/fltk
