> it's not just UTF-8 support that makes FLTK "would be better" library, there > is also cleaner interface, cleaner API, all things putted in namespace...
See my previous post about this. Putting code into namespaces does not makes cleaner api/interface, altought one will think they do. Going beyond simple hello world (no, I am not offending anyone here!) clearly shows something known as namespace lookup hell if caution is not taken. There is already collision with the system names, and if one would use anything advanced (especially system types and calls) it must use preprocessor hacks; this is not how I see clean interface (not to say that some people already reported uncompileable state on some devices due bad namespace support). > Sorry, but I don't agree that number of commits, solely, are so much relevant > in determining the ammount of effort that is being invested in development of > those two libraries. I might change only one, even C++ syntaxicaly, wrong > line of code, or even change some comment so doxygen generates proper docs in > future, that however does'nt meant that I contributed some new feature to the > library or corrected some bug. I'll bite :) So what are you considering 'a bug'? Doxygen can't generate proper docs, compiler errors, what are they? Program amusements? What you said is throwing away any single effort put into any code here (not to say how disrespects those who did that), no matter was that actual coding, giving advices, reports, discussions or just testing. Afaik, code is still not enough intelligent to fix itself and each commit/report/test/discussion requires some investment in it (nerves, time, stopping currently played movie; just name it). > As I said I'm not developer, but I know that FLTK 2.x is several years in > Alpha phaze, with full list of open bugs, almost all of you "route" new users > to FLTK 1.x because one can never fully count on FLTK 2.x (and who knows when > he could), while on the other side FLTK 1.x has recently reached version 1.8 > and is stable for a long time. Now, that should be also taken into account > when talking about attention being given to FLTK 1.x and FLTK 2.x. And this whole discussion is about that. -- Sanel _______________________________________________ fltk mailing list [email protected] http://lists.easysw.com/mailman/listinfo/fltk
