Hi Jeremy O'Donoghue: > That's the good news. The bad news is that this would once and for all > break compatibility with wxWidgets 2.4.2 as there have been many > changes in wx in the almost four years since it was released. > > So before committing what will be a sizeable patch, and one which > breaks API compatibility in some areas, I'd like a straw poll of > users' opinions as to what we should do. The options are:
I think we should go with latest version. In the future it might be a good idea to aim for the two latest major versions, as not all users can easily install the latest. But for now, I think we can live with only 2.8.something. And then keep supporting it until 3.2.something comes out. Or maybe we should support 2.8 until X number of months after 3.0 comes out. Greetings, Mads Lindstrøm ------------------------------------------------------------------------- This SF.net email is sponsored by: Splunk Inc. Still grepping through log files to find problems? Stop. Now Search log events and configuration files using AJAX and a browser. Download your FREE copy of Splunk now >> http://get.splunk.com/ _______________________________________________ wxhaskell-users mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/wxhaskell-users
