Hi All,
> >>>Perhaps we should try and move forward somehow. I've just looked
> >>>through the mailing list and there are several other bug fixes that
> >>>should be applied to any new build.
> >>
> >>In the short term,
> >>
> >>1) I'd be glad to contribute my fixes to anyone that cares, that would
> >>be willing to CVS-ize them, and make them generally available.
> >
> > I would be more than willing to bring the files together and serve
> > them up on jeb.ca
>
> Not sure whether this includes CVS-ing them? I'm guessing that it
> doesn't, but would do the other half, of making them generally available.
I'm registered as developper on Win32::GUI SoureForge project.
Theoricly, i have CVS access for commit change and tag version (not tested).
Aldo say on this mailing-list (7 april 2003 in Re: [perl-win32-gui-users]
The status of win32::gui)
> > What is the status of win32::gui - is it being actively developed? I
emailed
> > httptech a couple of days ago and just go lots of undeliverable
messages.
> yes, it is being actively developed. I'm currently working on the
> internals and I expect to have version 1.00 ready for Easter (but
> don't hold your breath on it).
> > It seems a few people in the last few days (Laurent Rocher and
Trevor
> > Garside) could actually move the project on if they had access to
the site.
>
> that's perfectly fine for me. please, anybody who want full access to
> the project on SourceForge (including CVS, file release, etc.) drop me
> a line with your SF username and I'll do it.
I'm waiting for new Win32-GUI Aldo's release.
But it's possible to fix some bug/miss on current release.
So I assume, Aldo agree for use sourceforge CVS to do this.
I think it's probably good to :
1) Tag current CVS source as 0.0.558
2) Commit and tag 0.0.665 sources
3) Commit new change over 0.0.665 source code (in a specific branch ?)
I'm not a CVS expert so i need to study how to do this.
If i can do step 1 and 2.
I can merge and apply your (and others) change to CVS.
I'm not here this week-end but can start to study this next week.
> >>2) I'd be willing to make available my binary distribution to anyone
> >>that wants my fixes (I've called it 0.0.668, since there were 3 fixes
> >>applied to 0.0.665), but I'm working on 0.0.669, adding more keys to the
> >>legal set of accelerator keys... all keys are legal accelerator keys to
> >>Windows, and only a subset were implemented in Win32::GUI.
>
> So would you put the .ppd and .tar.gz files up to, in a manner that PPM
> could use?
I have a PPM repository set on my Web Site.
I can put on it.
> >>3) I'd be willing to incorporate patches into my version, if someone
> >>identifies them, and sends me the patches, they aren't too cumbersome to
> >>apply, and make the merged binary distribution available.
I have made some change in 0.0.665 source code for build it for Perl
ActiveState with free MinGW compiler.
I think it's usefull for people want to build/contribute to Win32::GUI
source code without need of Visual C++.
Laurent.
