My opinion is that GuiTest is a weird mix of functions that are not really specific to testing. For that reason, it seems that the meat of those functions should reside in more appropriate modules (like Win32::GUI) and GuiTest (or any module specific to testing) should call those functions.
That being said, FindWindowLike in GuiTest can find childwindows, unlike the Win32::GUI counterpart. I do think that Win32::GUI could benefit from assimilating some parts of GuiTest. just my 2 cents... --- Jeremy White <[EMAIL PROTECTED]> wrote: > > >Or just merge their functionality, developer base, > and the technical > >prowess of the developers, to make both better, > less redundant, and more > >interoperative? > > Lots of interesting idea's. I've just had a quick > look at guitest.xs and > there does seem to be some over lap in functions > (such as > SetFocus,SendMessage, SetActiveWindow and many > others [there is the issue > about the AttachWin function that each of these > call]) so it would be > possible at the very least to have some sort of > common file that both > programmes can build from. > > Deeper integration, combining the strengths of both > tools and eliminating > some of the weaknesses would be a more work (I > think) - but conceptually, I > think it's a great idea. > > Cheers, > > jez. > > > > > ------------------------------------------------------- > 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/ >
