Hi Everyone,
This discussion was very informative. Since there is talk of changing the
module namespace anyway I was just wondering if the name could be changed to
something more descriptive - like Win32::GUI::Automate or something like
that? I had absolutely no idea on what GuiTest did until I read the
documentation on Piotr's website. Excellent documentation btw. And we could
leave the Win32::GUI::Test to the for the test scripts of Win32?
Being able to automate GUIs from within Perl would be really cool. I've
played aroud with VBScript and SendKeys - SendKeys dosent work on Terminal
Server windows for some reason. Specifically it dosent work on Citrix
terminal server sessions. However AutoIT from
http://www.autoitscript.com/autoit3/index.php works on Citrix terminal
server sessions. Maybe Win32::GuiTest could attempt to replicate some of the
features in AutoIT.
And finally if this could evolve to something like Internet Macros
http://www.iopus.com/iim/ then we would have arrived!
Warm regards,
Emmanuel
----- Original Message -----
From: "Robert May" <[EMAIL PROTECTED]>
To: <perl-win32-gui-users@lists.sourceforge.net>
Sent: Friday, October 07, 2005 3:27 PM
Subject: [perl-win32-gui-users] Re: Merging Win32::GUI and Win32::GuiTest
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.
-------------------------------------------------------
This SF.Net email is sponsored by:
Power Architecture Resource Center: Free content, downloads, discussions,
and more. http://solutions.newsforge.com/ibmarch.tmpl
_______________________________________________
Perl-Win32-GUI-Users mailing list
Perl-Win32-GUI-Users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/perl-win32-gui-users
http://perl-win32-gui.sourceforge.net/
