On Wed, 4 Apr 2012, Jeremy O'Donoghue wrote:
> I'm not quite comfortable moving to 1.0 - sounds a bit 'finished' to me.
Somehow yes. But wxhaskell is already very good and usable for my taste.
So 1.0 would be justified even for the current version. Even more we have
packages like HTTP with ver
On 4 April 2012 08:14, Henning Thielemann wrote:
>
> on a second thought ...
>
>
> On Tue, 3 Apr 2012, Jeremy O'Donoghue wrote:
>
> * The mainline will have the patches needed to update to support
>> wxWidgets 2.9.x, based on the work
>>
>>by Dave Tapley and others, and sourced from the dev
on a second thought ...
On Tue, 3 Apr 2012, Jeremy O'Donoghue wrote:
> * The mainline will have the patches needed to update to support wxWidgets
> 2.9.x, based on the work
> by Dave Tapley and others, and sourced from the development repositories
> on Darcsden, Readers of
> the wxha
On Tue, 3 Apr 2012, Jeremy O'Donoghue wrote:
> Please shout loudly and soon if you have any problem with what I am planning
> to do, as I am planning
> to make these changes within the next week. The wxWidgets 2.9 support has
> been waiting in limbo for
> too long now (my fault, I accept).
You
Hi wxHaskellers,
I am about to apply a fairly significant set of changes to the wxHaskell
master repository at code.haskell.org. This is in order that I can apply
the changes needed to support wxWidgets versions from 2.9 onwards, and the
major architectural changes this entails.
The changes will