I *finally* got the 1.04 release out of the door. I'll be interested to see how many problems we turn up now that it will get a wider circulation.

Most of the changes that I committed today are minor - fixing the build problems. On my machine I can cleanly build and test with perl 5.6.1 (MingGW and VC98), and perl 5.8.7 (MinGW, VC98 and cygwin gcc).

I've released source and binary builds, updated the documentation of the website, announced the release to the users and hackers list, and comp.lang.perl.misc/comp.lang.perl.announce.

I assume that a cygwin binary build will come from Reini shortly.

I also closed all the trackers that have been fix/included in the release.

At this point I need to take a bit of time off from Win32::GUI. I'll still be around, but won't be actively developing for a month or two. In this time I will be thinking about how I want to take things forward. I'm very tempted to start again from the ground up, as I think that there are core areas of the code that need re-thinking - more and more I'm seeing questions about how to do things that can only be done by making changes to the XS side of things; it would be so much better if other users could code solutions to their problems in perl and submit them as patches - it would lower the barrier to entry significantly.

Some of you will know that I have been thinking in this direction for some time. I will think about it some more, and if I think that it is the right way to go, I will code up a proof of concept to share with you all, and discuss before embarking seriously in that direction.

My thanks to everyone for their help; hopefully we can have a shorter period before the next release.

Regards,
Rob.
--
Robert May
Win32::GUI, a perl extension for native Win32 applications
http://perl-win32-gui.sourceforge.net/


Reply via email to