From: shelarcy <she...@gm...> - 2007-08-03 02:50:07
|
Hi Jeremy, On Thu, 02 Aug 2007 23:03:22 +0900, Jeremy O'Donoghue <jer...@gm...> wrote: > 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: > > Try to support latest wxWidgets I also vote to support latest version. > - Advantages > - We benefit from bugfixes and improvements in the base GUI library > - Simpler for new users, as getting 'historical' versions of wxWidgets means > you must compile it for yourself (which is non-trivial) as opposed to using > the version 'packaged' for your OS. Because I think these advantages are important for users. > - Disadvantages > - Due to changes in the way finalization is done in wxWidgets, it would no > longer be possible to use wxHaskell properly from GHCi as the underlying > wxWidgets library would be left in an unsuitable state once the first wxApp > event loop terminates. > Decide once and for all that wxHaskell is based on wxWidgets 2.4.2 > - Advantages > - GHCi works properly, at least on some platforms Okay, this property is important, too. But If we keep that wxHaskell is based on wxWidgets 2.4.2, I think that we must write complex build and user instuction for wxWidgets 2.4.2. (And to use latest wxWidgets.) Because some features require to use wxWidgets 2.6.x or higher, now. So we must write document to announce what is supported or not on 2.4.2. http://www.haskell.org/pipermail/haskell-cafe/2007-July/029439.html Best Regards, -- shelarcy <shelarcy hotmail.co.jp> http://page.freett.com/shelarcy/ |