On 18.04.2008, at 10:26, MacArthur, Ian (SELEX GALILEO, UK) wrote: > >>> The "hood is up" on the 1.3 tree (but only in a "lets not break >>> anything" way - whatever we put into svn absolutely *has* >> to be working) >>> so if you have code or patches to address this, nows the time! >>> >> >> Who me? I'm just a user :) > > Yes, me too. > But we know you can program, we've seen you do it. > >> Seriously, I didn't follow the "1.3 is now open" thread, so I wasn't >> aware that no re-engineering would be taking place. > > My take on it is that re-engineering is permitted, and even small API > changes, as long as they are demonstrably more sensible (or better yet > also provide backwards compatability to 1.1.8.) > But each step along the way has to "work", i.e. the svn image is > always > consistent and "stable". > >> To quote Emily Latella, "Never mind."
Well, the users are what makes the library. I am a user in the first place, but I also make additions to the core. I have taken 1.3 on to get a few additions in that I thought were really needed to get FLTK to current feature standards, so in short, FLTK 1.3 shall be FLTK 1.1.8 with: - UTF8/Unicode - a tree browser - a table widget - Doxygen documentation and a few rather minor improvments (code-wise minor, but often requested in this mailing list, like integer coordinates instead of shorts) This thread has already spewe out a great approach for the tree browser. It is starting get a little bit invasive, but only for the good of the browser. I would like to keep general re-engineering to a minimum for a simple reason: When we announced that 1.1.8 would be the alst of the 1.1, we ended up squeezing *everything* we could into 1.1.8, and it took us what, two years?, to get from 1.1.7 to 1.1.8. I saw links from other pages that said "development stopped", even though we were bug-fixing like crazy. But to the outside, it looked like the FLTK world had come to a halt. So FLTK 1.3 will contain thow four mostly independent changes, will be debugged and released. There is always a 1.4 that can contain a new round of independent changes, etc. . Trust me, I have already a list of 20 new features I'd love to have in 1.4 ;-) But in conclusion, all users, please contribute. Contibute ideas, patches, bug reports, let steam off, fix the docs. Any help is greatly appreciated. As you all know, this list ist generally very helpful, even trying to help n00bs over the crazyness of VisualC 5, never mind that it is not much related to FLTK ;-) Matthias ---- http://robowerk.com/ _______________________________________________ fltk mailing list [email protected] http://lists.easysw.com/mailman/listinfo/fltk
