> matthiasm wrote: >> ... >> 1: go strictly with our patch, remove duplicates, and clean up our >> API >> 2: use the already clean GLib API and hook that up with the guts from >> the patch >> 3: extract the unicode from GLib and replace code from the patch (but >> GLib is LGPL, FLTK is modified LGPL, so I am unsure if that is OK) >> 4: require GLib and link against it (my least favourite solution) >
Thanks for all the suggestions. I will use a combination of 1 and 2 then. I merge the code base with the patch (done), then make all the IDEs and Makefiles work that I can test (Linux, OSX, Xcode, VC6, VC7, VC8) and merge back into the trunk. The merge will allow other projects to continue (Doxygen, mainly). Now, this merged version will have some regression, so after the merge, I will start refactoring and fixing all Unicode support, hoping for support from the community (rgression testing, general testing, patches). I was very excited yesterday to see the first Japanese characters on my FLTK-for-OSX yesterday and I beleive that we are on a good path. Matthias ---- http://robowerk.com/ _______________________________________________ fltk-dev mailing list fltk-dev@easysw.com http://lists.easysw.com/mailman/listinfo/fltk-dev
