Hello, FLTK-1.1.8 will sometimes be released I'd guess and of course welcome. Fascinatingly the utf-8 version is following close. Now that I used utf-8 in some of the applications I try to maintain, it would be of great help to have the UTF-8 version distributed.
One technical point are the header files, which should not be intermixed between both FLTK1 versions. o saying that only one version should be installed seems not appropriate for two different packages o modifying the include path would be out of scope for most projects o adding a new prefix to the UTF-8 version requires some amount of work in the projects, which like to use the nice feature. Anyway this would be possible. o combine both with the headers installed from the UTF-8 version and both library versions One thing, which I am not shure whether it really helps is the fact of every project should be able to start a clean compile from scratch with FLTK1.UTF-8 . Would it make sense to not to install the backward style FLTK1 headers and just the backward libraries? Of course both version would be in need to bring into one package. The backward libraries would be named to all those old names, which make old applications happy and the utf-8 libs could pick something else, which it already does. Still I am not shure if this makes sense to a plug-in / host relation with one part being old style linked to say FLTK-1.1.7 and one to the UTF-8 enabled version. Would they fail badly or see I problems where no is to be expected? ... other options to make FLTK1-UTF8 distributeable ... thanks for the great work so far, Kai-Uwe Behrmann -- developing for colour management www.behrmann.name + www.oyranos.org _______________________________________________ fltk mailing list [email protected] http://lists.easysw.com/mailman/listinfo/fltk
