Here's what things look like from this user's perspective. The main goal of the 1.3 version is going to be merging of 2.0 and 1.x into a single trunk, while providing an easy migration path for users of both existing branches. The idea being, if I understand correctly, to coalesce existing camps of developers and avoid further splintering.
That's good and well, but I'd like to point out in a neutral non-judgemental way that it's a good sized job whose benefit to users is almost vanishingly small. What would motivate a user of either fltk 2.0 or 1.x (not an fltk developer) to upgrade an existing application to 3.0? It apparently offers no new features, fixes no bugs, and doesn't improve performance. What about new development? I suppose one would be motivated to upgrade if the older branches were in danger of becoming unsupported, though, as somebody (Matt?) pointed out, one thing about open source is that you can always support it yourself if you want to. Other than that, why upgrade? The new api would have to be a LOT nicer; the fact that the new api is close enough to the old one to allow a compatibility layer to exist makes it very unlikely (imo) that such is the case. Now, I understand that the 2.0/1.x thing has become sort of an ugly mess. If resources were free and infinite I'm sure that cleaning it up would be a Good Thing. I'd be concerned, however, that devoting a lot of energy to a gigantic merge whose end result is not a better product than what already exists may not be the best allocation of time and resources. Best, Stan _______________________________________________ fltk mailing list [email protected] http://lists.easysw.com/mailman/listinfo/fltk
