> This roadmap is a result of polls and mail conversations after the > 1.1.8/9 release earlier this year. FLTK1 and FLTK2 have a user group > with a large code base. For example, my code base (many hundreds of > thousands of lines of code) uses FLTK1. Some of my apps are > commercial, one runns CNC-milling machines (a crash in this app can > cost serious money or even hurt people), some are OpenSource with 60 > or so users. > > All these projects have in common that I have to rely on the libraries > I use. Using FLTK2 is out of the question at this point - believe me, > I tried. I understand that. And that's why if fltk1 and fltk2 continue to develop separately, fltk2 will most likely just get abandoned some day. > Unless you have a near-perfect compatibility layer and the trust of > the users, no FLTK1 users will use that hybrid. It will take years to > reach the reliability of F1. I propose the following way of developing: 0. Create new lib fltk-base as a part of fltk project. 1. Make both fltk1 and fltk2 build with it. 2. We take some part of fltk1 code(for example, filename functions) 3. Move them to fltk-base without changes to the code, just renaming them(for ex. fl_filename_absolute -> fltk::fs::filename_absolute, or something). 4. fltk1 team accommodate fltk1 to use this new api. 5. The same for fltk2. If a function has different semantics in fltk2 - discuss it, and either make fltk2 use it as is, or(if fltk2 semantics are really superior) replace it with fltk2 variant, or rewrite it. 6. If function semantics have changed, either accomodate fltk1 to the changes, or write a adaptor. 7. Test it. If changes were non-trivial, test it again. 8. Look through bug trackers, check related bugs. 9. Drink some beer 10. goto 2
This is not a hybrid, this is refactoring. > I agree. If you manage to motivate enough reliable dvelopers, I will > join the merging process. I will not abandon F1 though for the reasons > mentioned above. Since I don't know any of developers in person, I can only write something on this ML: Reliable developers! Are you motivated? If yes, write about it. If not, write about it, make clear your point. I myself will contribute on fltk2 part when I have time. _______________________________________________ fltk-dev mailing list [email protected] http://lists.easysw.com/mailman/listinfo/fltk-dev
