Fabio Bracci wrote: > Hi, > I believe that 1.3 it's pretty stable ... but why then hasn't it been > officially released as stable?
You may think that it is stable, but there are still development efforts, and I would bet that there will be some more ABI changes before we can do an official release. Once we have an official release, the ABI is fixed, and we can't change anything ABI related. Another point is that the new utf-8 code is (IMHO) far from final, WRT foreign language and character set input (Chinese, Right To Left, and some more problems). Others may correct me here ... > Moreover, I think I saw a bug report mentioning API changes between 1.1.x and > 1.3, but those changes aren't documented .. is it? There are only a few API changes, and this is intentional. There is a chapter about Migration in the docs. > I was already considering fixing something in 1.1.9, but indeed then I'm on > my own and its' pretty convenient to lift with the framework's improvements > ... If you really want to fix something in your local copy and still get improvements, then subversion is the tool to use. You can modify your local copy, but also update it with new versions. > To the other side, I'm a fltk novice and it's pretty time -consuming to dig > in to such a level that lets me modify the framework without making a mess of > it. > > another thought: it seems to me nobody wants to fix anything in 1.1.9, why is > that? It's a matter of man power. This is open source software, and all the developers are doing this (mostly) in their spare time. You're invited to help ;-) > as long as there isn't any other stable release, I'd think i'ts worth to > merge bugfixes, at least the lightweight, like this draw()-related one. I'm trying to do some more fixes for FLTK 1.1, and I think that 1.1.10 is coming soon. But just this "draw()-related" one is not lightweight. Changing the protection of (a) method(s) is likely to break ABI compatibility, and we can't do that for 1.1. And the protection of the draw() methods is NOT a bug, it's a design decision! And there's a workaround. If there are really serious bugs, they will be fixed (if we can). Albrecht _______________________________________________ fltk mailing list [email protected] http://lists.easysw.com/mailman/listinfo/fltk
