Matthias Melcher wrote: > On 22.02.2010, at 10:19, MacArthur, Ian (SELEX GALILEO, UK) wrote: > >>>>> Indeed this printing patch was done through device abstraction. >>>> That sounds just fantastic! Can we still combine this with the >>>> work done for 1.3 printing? >>> Q. Will the release of 1.3.0 fix the API/ABI for the 1.3.x series? >> I imagine that it would. >> >> And that the device abstraction would change the ABI in an incompatible >> way (though the API might look the same to the programmer - again, I >> assume that it would *look* the same.) >> >> So if we push out 1.3 without device abstraction, then device >> abstraction has to go into 1.4, since we can't assume that everything >> linked to fltk-1,3 will be static. > > Ah, well, yeah. I guess we should push 1.3.0 out very soon, even if printing > is experimental. There are still some utf8 flaws though that should go first > :-/
Agreed. Although the device abstraction is very interesting, it would IMHO be too big to do it before the release of 1.3.0. We can merge the current printing support back in the main 1.3 branch, and then we can release 1.3 after fixing the remaining UTF-8 things. With or without Linux/PS printing, if this would be too complicated or too bad with only printing images. Full device abstraction should then be the next step and consequently in the next release 1.4 (unless the 2.0 merger would happen as well, and this would be 3.0). But I think that we should do device abstraction _before_ trying to do the 2.0/1.x merger. Albrecht _______________________________________________ fltk-dev mailing list [email protected] http://lists.easysw.com/mailman/listinfo/fltk-dev
