> But our projects have been done by using fltk2.0, if we moving to fltk1.3, I > think > many work need to do, because the API is a bit different.
Might still be better to do that porting work - if you need to support the code in the longer term, fltk-1.3 is a more robust basis than fltk2, as things stand. Though if the code is a one-off, then maybe it does not matter. Remember that overall, the through-life cost of supporting the s/w will generally outweigh the up-front cost of creating it in the first place, so spending a little extra now to reduce your maintenance burden will save you money overall. 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
