Dejan Lekic skrev: > Well, I use FLTK 2.0 for a pretty serious project with deadline at the > end of April. I would say it is pretty much stable. Sure there are some > problems, but I fix them on the fly, or use some workarounds. If you > chose FLTK 2.0, please feel free to either write here, or e-mail me > directly.
I'm also using FLTK 2.0 for a large, commercial application which is about to be released. I've also found the core to be very stable (stable as in few/no crashes related to bugs in the main library code). I use a lot of custom widgets, and relatively few of the more exotic widgets that for a while were changed rapidly. I chose 2.0 for several reasons, some of which will be outdated when 1.3 is available in a somewhat finished version. However, 2.0 still has some advantages in its API and structure, e.g, the difference in coordinate systems and layout. If you start with 1.3 or 2.0 and change your mind, you can always rewrite your code later. I did this when I found I needed UTF-8 support, and it's certainly possible (although a very, very boring task). Try both on the platforms that you need to work, and choose the one which fits your needs best. Some possible problems with 2.0: - Lack of active development. If you look at the number of bugs and the commits related to 2.0, it looks quite dead. I looked at the bug lists, and most are outdated, some are specific to obscure platforms (cross compilation etc.), and a few should be fixed. None of the bugs have been a real problem for me. The main issue is that lately there doesn't seem to be anyone taking care of the project management, and the future is uncertain. - Sometimes in the past a developer has performed massive updates of the source code in one session, leaving certain things in a not quite finished state. If I were to start a new project right now, I'm honestly not certain which toolkit I would use. I guess FLTK 1.3 is logically the best choice, but I really dislike certain things with the 1.x branch, like the coordinate system not being relative to the current widget. Unfortunately, there are very few alternatives when you want a small, stable, cross-platform GUI library with OpenGL support. I guess I want the final 1.3 core with 2.0 API. Arne Magnus Bakke _______________________________________________ fltk mailing list [email protected] http://lists.easysw.com/mailman/listinfo/fltk
