On 27.02.2008, at 03:02, Roman Kantor wrote: > matthiasm wrote: > >> 5: class by class, take the FLTK1 API and replace it with the FLTK2 >> API, >> staying compatible to 1.1 at every point. The only really hard thing > > I would really keep the 1.1. source compatibility as much as possible. > In many cases you can have compatibility headers between 1.x and 2 > easily done but such changes are more-less just a syntactic sugar. But > when I had a look in FLTK2, the really interesting things would break > the compatibility and would be difficult to have 99% compatible. > If you jump to 2.0 api you will make the same mistake again. Better > making small steps keeping the code in "nearly production quality" all > the time. This is proven approach with fltk 1.1 where svn was good > quality at any moment.
Oh yes, I do not like to break any code at all. I would go function-by- function and verify compatibility to 1.1 and 2.1 at all times. Just as we did in 1.1 all the time. The 1.0-to-2.0 jump was doomed because 1.0 users were unable (and unwilling) to upgrade their source base and created 1.1 instead. A 3.0 would have to grow to be compatible to 1.1 *and* 2.1 before we do any greater changes, or we will split the entire user base once more. > I think breaking binary ABI more often is not a > problem but source compatibility should be kept quite strictly. Yes, absolutely. >> 6: now we can copy more essential features of FLTK2 over to FLTK3 >> (printing, symbols, doxygen, etc.) > > For printing devices I would not be affraid to be cairo-dependet Well, I see this like I see everything else in FLTK: there should be one implementation using the minimal capabilities provided by the OS. FLUID1 already has printing built-in, and Mike is an expert here for Linux and OS X anyways. Cairo, to me, is just another possible driver for graphics output. The less external dependencies we create the better.The jjpeg and zlib libraries which we use, for example, are absolutely final, so they require no maintnance on our side: perfect. Matthias ---- http://robowerk.com/ _______________________________________________ fltk mailing list [email protected] http://lists.easysw.com/mailman/listinfo/fltk
