Is the design of the "wrappers" in fltk3.0 intended to allow the widget's to be *completely* different, in that they can have different sets of virtual functions (such as changing the arguments, removing some, etc), different hierarchies of objects, and reuse names from 1.0 for different purposes (like making x() be relative, while the 1.0 wrapper still returns absolute)?
I'm going to assume this is true for any further discussion. There should now be an ability to, if wanted, completely rewrite all the widgets. This may offer a lot more freedom than 1.0. The biggest question is exactly what to do if such rewriting is attempted. Is there a plan to stop contributions to the fltk1 branch, or to carefully reproduce any and all fixes in fltk3, even if the base code diverges a lot? The loss of all fixes to fltk1 in fltk2 is what killed it, apparently. _______________________________________________ fltk-dev mailing list [email protected] http://lists.easysw.com/mailman/listinfo/fltk-dev
