> In my opinion, any code injection and any run-time > costs/features should be > optional. I would suggest that you use templates (policy > traits) to enable > users to mix-n-match the things that they want. At least, I > do not want any > run-time code injection. If I want that feature, i can do > that on top of > fltk. Including this in FLTK would mean making it top-heavy.
Asif, You may have misunderstood the thrust of what Matt is doing. In particular if you use the "native fltk3" API there is no cost - there is only a (small) cost if you are using (for example) fltk-1.3 source-code in a fltk3 runtime... 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 mailing list [email protected] http://lists.easysw.com/mailman/listinfo/fltk
