In article <[EMAIL PROTECTED]>, Cameron King <[EMAIL PROTECTED]> wrote:
> I liked the 1.1.x series. > > Why after 1.1.7 is there 1.1.8 and 1.1.9. What's the difference between them? > > Why is 1.3.x now being developed in the SVN instead of effort primarily into > the 2.x.x series? > > Is this legacy-gone-mad, or experimental branches? This is probably just out of necessity. Like you said, we like 1.1. It's stable, and has been through a lot of debugging. 2.0 has a nice API, but it hasn't the same kind of maturity and API stability that would allow you to base a long-lived project on. This greatly reduced the amount of manpower behind FLTK 2.0. Since 1.1 was blocked by API constrains, we couldn't fix some bugs or improve some features. Many kept patching FLTK locally. 1.3 is an attempt to unblock the situation. This will allow us to improve the API and feature support by reusing the stable codebase, someday incorporating much of the stuff present in FLTK 2. There are/were a lot of custom FLTK 1.1 customizations out there just because of the API constrains. UTF-8 is the primary one that is being merged right now. I personally like this approach. FLTK 2.0 would take years at the current development speed to get to the same stability of 1.x. _______________________________________________ fltk mailing list [email protected] http://lists.easysw.com/mailman/listinfo/fltk
