From: Aldo Calpini <[EMAIL PROTECTED]>
and I'm very, very happy to see things moving and people willing to
help. as it is clear at this point, I'm not in the position to continue
developing Win32::GUI all alone. but I'm not going to give up the project.
if there is something useful for the community I can do acting as a
coordinator (sort of "pumpking", in Perl terms), I'll be very happy to
coordinate. if someone feels like taking over the whole stuff, I'll be
very happy to be just a member of a team of developers.
I think one thing we can all agree on is that we have missed the role of a
coordinator and figurehead. Welcome back:)
my current development version of Win32::GUI has many bugfixes, but the
internals are being heavily reworked (to support NEM more "natively")
and there are many non-working features. as an open question to anyone
interested, I ask: do you think it is better to keep the "rewrite" off
for a while and work on bugfixing the current release, or do you
prefer working with me on the new internals?
From a personal viewpoint - maintaining two or more code lines always ends
up in a mess. However, there is a legitimate need to get a new build out
with all the bug fixes and minor improvements. Once a new build is released,
focus should back to the new development.
regarding the documentation, I appreciate what Erick did, but I found
it a little difficult to work with. I think a wiki (with CGI::Kwiki,
for example) would be a better start. we could also write in POD so
that the documentation could be more easily integrated in the CPAN
distribution.
I quite liked what Erick did - but your the boss:) I think Win32::GUI does
need a document project of some sort - it takes alot of the druggery out the
process. Perhaps Erick could set up something under sourceforge and make the
sourceforge website the "home" of Win32::GUI?
Cheers,
jez.
_________________________________________________________________
It's fast, it's easy and it's free. Get MSN Messenger today!
http://www.msn.co.uk/messenger
