Hi folks. I just would like to add my thoughts here.
I know this has been discussed in the past but, in my opinion, I don't understand what is the value of creating a new version (fltk3) if we don't have neither fltk1.3 nor fltk2 stable. Instead of creating a new version, why don't we fix the current versions? With fltk1.1 done - and very well done, I have to say - I believe we have more hands to work with fltk1.3 and fltk2. I understand some folks like the way fltk1.1 API works and they will probably keep working with fltk1.3, but fltk2 is a very nice API, with a lot of folks using it - e.gl dillo project and myself. I've contributed with some code to fltk2, but I got frustrated when I saw just a few folks - to name Albrecht (thanks man) - took the time to review it and the code is stuck because nobody with enough knowledge about the API could double check it. I'm checking the fltk poll this week and I can see that after fltk1.1 it's fltk2 the people use and not fltk1.3 as I've heard some folks talking on this forum (and on dev as well). So, I believe we should rethink this whole idea for now. Put it in hold and when we have fltk2 and fltk1.3 in stable state, we could move forward with next step, i.e. unifying them. But again, this is just my opinion. Thanks for the opportunity to share it. -- Isaque Galdino "sic enim dilexit Deus mundum ut Filium suum unigenitum daret ut omnis qui credit in eum non pereat sed habeat vitam aeternam" -- Iohannes 3:16 _______________________________________________ fltk mailing list [email protected] http://lists.easysw.com/mailman/listinfo/fltk
