> BTW: I included preferences.cxx/.h because FLTK3 Fluid at the > moment would write a mishmashed FLTK3 cxx/h pair. In an > effort to generate the FLTK3 FileChooser UI from the .fl > file, I forgot that an FLTK1 .fl file should still generate > FLTK1 code, and an F3 .fl file should generate F3 code. > Optionally, an F1 .fl file should be saved (exported) as an > F3 .fl file, which will of course fail for user generated code.
Oh, that's a point - it had not occurred to me that we will need a "super-fluid" that can create fltk1 and/or fltk3 (or even fltk2) source as its output. That's quite tricky. How do we even represent that? Does the fluid file specify what output-style it should be, or does the user click a check-box when generating the code, or...? > But I will get to that when everything else works. Indeed... SELEX Galileo Ltd Registered Office: Sigma House, Christopher Martin Road, Basildon, Essex SS14 3EL A company registered in England & Wales. Company no. 02426132 ******************************************************************** This email and any attachments are confidential to the intended recipient and may also be privileged. If you are not the intended recipient please delete it from your system and notify the sender. You should not copy it or use it for any purpose nor disclose or distribute its contents to any other person. ******************************************************************** _______________________________________________ fltk-dev mailing list [email protected] http://lists.easysw.com/mailman/listinfo/fltk-dev
