Am 16.04.2009 10:03 Uhr schrieb "Duncan Gibson" unter
<[email protected]>:
> Matt:
> In "[Library] r6765 - in branches/branch-1.3: . FL src test"
> http://www.fltk.org/newsgroups.php?gfltk.commit+v:7120
>
> I see that you enabled putting the doxygen commentary for the UTF8
> functions into their own doxygen module. Are you actively working on
> the unicode.dox page as well?
No, I am not. I merely added this doxygen command to get an overview of what
could be a complete list of Unicode commands. Please feel free to remove and
move around whatever is needed.
> After updating the background info in unicode.dox last week, I was
> hoping to start on at least listing the UTF8 functions on the page,
> [with FLTK2 and OksiD tags showing their origin for the moment],
> to at least gather the things into a single place for reference.
> But if you are already working on it...
Yeah, we had the same idea. I like your approach more than mine (gather the
information first). My startegy is to fix Fl_Input and Fl_Text_xxx and
reorganize whenever I need something. This is potentially incomplete ad
requires major cleaning up every once in a while. A more systematic approach
would be nice.
> Also, is the plan to "merge" the FLTK2 stuff into the OksiD code,
> or "merge" the OksiD code into the FLTK2 stuff, or produce a hybrid
> third way. In other words, will the FLTK1 UTF8 code present a similar
> API to the FLTK2 UTF8 code, or will it be a completely new beast?
Another mistake on my side: I was planning to add and rename as I go. It
would be much more useful to be compatible with FLTK2.
(time passes ;-)
OK, I looked at the FLTK2 interface. I believe we should stick with and
extend that API. I case we ever merge, we all have one headache less. One
thig though that I would like to recommend: let's keep the Unicode API truly
plain "C". It is included by other plain "C" interfaces within FLTK.
I have a few ideas on speed-optimization, assuming that most text will be
ASCII with some additional interntional characters. This will be great for
Europeans and not hinder too much non-ASCII languages.
Anyway, don't worry about fiddeling in my code. I do try to submit changes
that are complete within their functionality, but there is no guarantee that
I don't ruin other code.
Matthias
_______________________________________________
fltk-dev mailing list
[email protected]
http://lists.easysw.com/mailman/listinfo/fltk-dev
