Sanel Zukan wrote: > +1 > > Looking at the logs, there is a hell of core changes! I have to ask this: > will be there drastic break-all-current-code-all-over-the-world changes again > ?
I would expect a few more changes that might break existing 2.x code, but hopefully not too much (i.e. it might just be renaming or revamping the current functionality to make it more consistent all around or fix a fundamental problem...) > Current api stabilized very much and rest-of-the-world is not very > keen to update their code to the changes. It would be nice if someone > could post here something like a roadmap of drastic changes so some user > don't get a heart attack when it's code is unable to compile with > the latest revision. We've never guaranteed API stability in the 2.0 snapshots, and in fact I (and others) have long harped on the lack of stability in 2.0 as a reason to avoid it for production use. Once 2.0 is actually released, we'll be changing our tune... > Btw. (althought in the log is stated) are there real needs to remove > all those members from Group, removing that small amount of > compatibility with the 1.x code ? Can we hear thoughts from the others ? As I understand it, Bill is moving the child support from Group to Widget; functionally this should not affect existing widgets once Bill is done with the reorg, and the 1.x compatibility headers will handle any mapping that is needed... -- ______________________________________________________________________ Michael Sweet, Easy Software Products mike at easysw dot com Internet Printing and Document Software http://www.easysw.com _______________________________________________ fltk-dev mailing list [email protected] http://lists.easysw.com/mailman/listinfo/fltk-dev
