I'll add some of my opinions from the perspective of a user; please forgive if I reiterate some points.
First, +1 on UTF8 and printing support being added to 1.1.8. I have just released a product commercially where the user interface is based entirely on FLTK (www.3dop.com)!!! I have often wondered how nice it would be to have international support. As for printing, doing it cross platform was a real pain. FLTK would definitely benefit from its addition. Second, I follow FLTK's development pretty closely. I literally check the web site everyday, especially with the release of 1.1.8 so imminent. I don't need to say that FLTK 1.1.8 is one solid and stable piece of code. It would be a real shame to discontinue any feature development on it (other than bug fixes). Third, I think that a nice but not essential feature would be a proper callback or signal/slot type mechanism built into FLTK. I say not essential because you can always use boost for that type of thing, but having it built into the library would lead to much cleaner FLTK code IMO. Now this feature would be nice for the obvious reasons: A type safe to pass parameters of arbitrary length and type between widgets. My two cents :) Dave > > On May 29, 2007, at 4:33 AM, Millan wrote: > > > I don't know if I'm entitled to discuss this, because I'm not FLTK 1|2 > > developer, I'm just using it, but since people who actually work on > > it, > > initiated this discussion here, I'm assuming they would also like > > to hear > > opinions of library users. So here's my crop. > > Absolutely. Please! I started this specifically to get the opinion of > the users. I mostly know the opinions of the developers, but we are > not writing this library for us alone (or at least we should not ;-). > > I really hope that as many users as possible chime in and give their > opinion. This was a long weekend in parts of Europe as well, so I > will let this thread run a lot longer before summing it up. > > Thank you very much for you words on FLTK1 vs. FLTK2 development. > This pretty much described the two chairs that we sit between: FLTK2 > development has been slooooow at best. There hasn't been any major > bug fixing in months and the STR list grows. Sure, there is > frustration on the FLTK2 side because FLTK1 got a lot more attention > in the last months, but that's what "finalizing" is all about. > > Just the last two mails imply that finalizing the FLTK1 branch and > continuing with FLTK2 will cost us users, and not concentrating on > FLTK2 will cost us user as well. I would love to know which action > will *bring* us new users and what will make the *stay* and even > *contribute* in the long run? > > Again, I am writing this library for others to use, and for myself. > But if it gets to the point where I only support six remaining users, > I will switch libraries as well... . > > Matthias > > ---- > http://robowerk.com/ > > _______________________________________________ fltk mailing list [email protected] http://lists.easysw.com/mailman/listinfo/fltk
