> Hi Don, > > I'm replying to this old post, because we're just (again) discussing the > removal of forms compatibility from FLTK 1.3 [1]. > > D. Zimmer wrote: > > I am in the process of converting an xforms application to use fltk, > > and as a result, will be coding some of the missing bits not provided > > by the compatibility header (gl_canvas, fl_XXX_pup() etc.). > > [...] > > Are you still interested in / using the forms compatibility > headers? What is/was your progress? > > Did you finally rewrite your application(s) to "native" FLTK > code? > > Albrecht > > P.S.: CC to your mail address, because I don't know if you're > currently following fltk.development. > > [1] http://www.fltk.org/newsgroups.php?gfltk.development+v:7760 > > -- > remove S P A M for mail
I do still lurk here on occasion. I did not port my app to native fltk, but rather extended xforms compatibility with a static library formsx.lib which can be got from: http://www.magma.ca/~dzimmer/code/formsx.zip (60k) Anyone should feel free to canibalize this code as they see fit. Keep in mind that the application started out using a customized version of GL forms, then was ported to xforms, and finally FLTK, so there is a handfull of obsolete functions which no longer do much of anything, as well as functions beyond what is provided in xforms. My focus was just getting the darned thing to compile with minimal changes, so a fair bit was compromise (wasn't going to recreate XEvents). I did however work out several tricks for painlessly adapting code written for the "FDUI" structure emitted by the xforms forms designer, to that emitted by fluid. I would be willing to do up a readme.txt, if ever anyone requests it (is there really anyone still around who would need this, I wonder). I personally, see little point in maintaining forms compatibility beyond 1.1.x (or GLUT for that matter, but I realize that may be an unpopular opinion). I just feel that the core FLTK distribution should be streamlined, and support for alternate API's could be maintained separately. Cheers, Don. _______________________________________________ fltk-dev mailing list [email protected] http://lists.easysw.com/mailman/listinfo/fltk-dev
