> 1: Greg's right. We should finish 1.3 first and release at least 1.3.0
Yes. Though I think we are maybe "near enough" already... > 2: the porting is stupid boring manual labour ;-), basically > a huge find and replace, which must be fully automatic Though hopefully without breaking the makefiles! > 3: the FLTK1 wrappers are quite simple and could be semi-automatic Could be - though some (e.g. the GL worappers?) might need some extra clever thought? > 4: the FLTK2 wrappers need full attention by experienced > developers, but when implemented will add great features to > FLTK3 that FLTK1 users can then use too Yes - though we need to be careful - a lot of widgets were added to fltk2 core that look like they were probably just some passing devs hobbyhorse, those devs moved on, and these things are now unmaintained carbuncles, in my opinion. So lets not port *all* of fltk2 - let's port the bits that are "good" and if we port the rest at all, let's put it in some non-core lib. Also, fltk2 has various attempts at themes, currently mostly broken, so I don't believe we should stress to much over porting all of that cruft over either. > So let's get 1.3.0 out. Yes. 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
