These are the points that I see as being important. - 1.3 is more important than 2.0 as it's stable+released and has many more followers - Having a stable version - Devs willing to work on maintaining FLTK (like Matt)
What were the reasons that we had 2.0 in the first place. From what I understand it was mainly the cleaner looking API (namespace) and UTF8. Now 1.3 has UTF8. So if Matt has almost (95%) completed 3.0 port of 1.3 and it has a cleaner API then why would anyone want to stick with 2.0? BTW Matt can you post up "Hello World" (from hello.cxx listing 1 in 1.3 FLTK Basics doc) in 3.0 syntax. What's wrong with leaving 2.0 behind forever? We learned much from 2.0 and we can selectively cherry pick some of the best ideas/features in the future (as we did for 1.3). Personally, I see the real question as not should we merge 2.0, but rather what should be the future of 1.3? On that note I do think it's important that FLTK stay lean. ie No STL. As other toolkits get fatter and fatter if we stay lean it will be easier for us to be adapted to different platforms ( eg mobile devices) Also as a user of pyFLTK I really see the benefit of making FLTK easier to have bindings for other scripting languages. Having my own Open Source project I also know it's important we don't demand too much from people like Matt for fear they will burn out. Think about it in terms of what we need, not what we want. Cheers -- Robert Arkiletian Eric Hamber Secondary, Vancouver, Canada _______________________________________________ fltk mailing list [email protected] http://lists.easysw.com/mailman/listinfo/fltk
