Piotr Kaluski wrote:
1. Win32::GUI team has a look on what is implemented in Win32::GuiTest. Have a look on the manual. It is up to date: http://www.piotrkaluski.com/files/winguitest/docs/index.html . The source code is available at www.sourceforge.net/projects/winguitest.
I'll certainly have a look, but it may be a couple of weeks before I get the time to do this.
2. We figure out what is already available and what has to be ported to Win32::GUI (remember about interprocess boundary problems, see the manual, "Advanced tutorial").
Seems reasonable.
3. Win32::GUI team ads new functions to their module.
I think there is a decision to be made between steps 2 and 3. Another possibility would be for the Win32::GuiTest team to take on the responsibility for development of Win32::GUI::Test, possibly even as a separate project, and just use Win32::GUI. It sounds like you don't have much development effort in your group - I'm not sure that we have a whole lot here either. But let's wait and see how much work we think is involved.
> Just one more think. I believe this discussion is important, since it may
have serious impact in both components. Therefore I suggest that we submit all posts to the perl-win32-gui-users@lists.sourceforge.net list and we avoid e-mails sent to individual people directly. It will help others to follow the progress of the discussion.
I would suggest moving this discussion to the hackers list which is much more suited for development issues (You will need to subscribe if you have not already). I have set 'Reply-To: [EMAIL PROTECTED]'
Regards, Rob.
