Me: >> There was talk of trying to define a common low-level interface to >> the UTF-8 stuff that could > be shared by both FLTK-1.3.x and FLTK2. >> After the 1.3.x release of course.
Gerry: > Perhaps you can clear something up for me. Is FLTK2 the ultimate goal > or is 1.3.x going to slowly evolve into what FLTK2 was intended to be? IMHO There isn't really a clear-cut Yes/No answer to either question. The main features that FLTK-1.1 doesn't have that FLTK-2 does offer, and that people would like to see added into 1.3.x, are UTF-8, skins or themes, and printer support. All of these are add-on features that should not require major rework of existing FLTK-1 applications. *If* it is possible to add these features and create a common interface library that can be shared between FLTK-1 and FLTK2 then we all benefit from a reduced code base, with only one set of bugs to fix. We now have parallel code streams where FLTK-1 developers have fixed a lot of bugs that affected their applications, but many of these fixes have never been applied to the FLTK-2 code [fewer developers and applications?] FLTK-2 also introduced changes to the class hierarchy (eg added Symbol) and to the code structure (eg namespaces) which therefore may entail a lot more work for someone trying to port from FLTK-1 to FLTK-2. I have not done this, so maybe someone else can comment on this. We don't have the resources of some of the other toolkits like Qt. We have a small number of active developers for FLTK-1, with even fewer developers for FLTK-2. If we can re-use effort spent on FLTK-1 to help FLTK-2, that can only be a good thing. Especially with recent renewed interest in FLTK-2 (e.g. for dillo). We can't merge FLTK-2 back into FLTK-1 overnight, because it would involve too many changes for both sets of applications, but the more code we can harmonise and share, the easier it might be to merge future generations of FLTK-1.3.x and FLTK-2 to produce a single FLTK-3 or FLTK-4. Possible? Or just a pipedream? D. _______________________________________________ fltk mailing list [email protected] http://lists.easysw.com/mailman/listinfo/fltk
