Evan Laforge wrote: > So in the short term it looks like fltk gets by with its own > implementation, because using the OS one is too much work. Entering > Chinese with a character palette is not really practical, it would be > much easier to just write in another app and then paste it into the > fltk text input. This works but isn't ideal, so in the medium to long > term, it would be nice to use the native input widget, which would > also provide a usable Fl_Text_Display.
IMHO you're missing an important point here: FLTK's cross platform compatibility. If we would use native Fl_<something> widgets on one platform, you couldn't derive your own widgets in a cross platform way. My own application, for instance, derives own widgets from Fl_Input and uses handle() to filter keypresses and does some more things. What, if the Mac version would use a native widget "under the hood" of Fl_Input? Not to speak about identical behavior of the same app. on different platforms, but that's a question that can't be answered generally. Dependent on the user base, someone who has more experience on a Mac would more like the Mac way, but someone who knows an app. on Windows (or works with the same app. on different platforms) would probably want it to behave identically on all platforms. I know that there are reasons to add platform specific stuff (like system menus, native file chooser, etc.), but probably better not in such essential widgets like Fl_Input (and Fl_Text_Display/Fl_Text_Editor). Albrecht _______________________________________________ fltk-dev mailing list [email protected] http://lists.easysw.com/mailman/listinfo/fltk-dev
