On 20.06.2008, at 14:07, MacArthur, Ian (SELEX GALILEO, UK) wrote: > When we do the merge, and we find differences between the nominally > similar F1 and F2 implementations, how do we choose between them?
The code should follow a similar basic structure. After all, FLTK2 *is* based on FLTK1. We should read through the code and understand why the code differs and choose the sections that seem correct, keeping in mind that F1 is extremely stable, but F2 already having UTF-8 built-in. I hope that the core does not differ too much. I know that the OS X code for one was only added two years ago and has since then seen ifferent(!) bug fixes in F1 and F2. A merger here should solve the last remaining F1 OS X opsies as well ;-) - until we move away from Carbon to Cocoa and have to rewrite half of the code anyways... . Sigh. > Also, how do we decide exactly what the F2 API is, as it still seems > to > change...? Still, with this approach, maybe that doesn't matter so > much... The F2 API is indeed much better, but there are still a few inconsistencies. For F3, I would re-read the coding standars document <http://fltk.org/cmp.php#CODING_STANDARDS > and change the API to match thoroughly. If we follow the process as described, we will reduce the F1 and F2 parts of the new project into a source-code level compatibility layer which will even out most differences to F3. We can always test back-compatibility by keeping the F1 and F2 test directories around until we are satisfied with F3. Matthias ---- http://robowerk.com/ _______________________________________________ fltk-dev mailing list [email protected] http://lists.easysw.com/mailman/listinfo/fltk-dev
