From: Jeremy W. <jez...@ho...> - 2005-10-06 18:25:31
|
>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. |
From: Ariel S. <as...@ya...> - 2005-10-06 20:02:54
|
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 <jez...@ho...> 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 > Per...@li... > https://lists.sourceforge.net/lists/listinfo/perl-win32-gui-users > http://perl-win32-gui.sourceforge.net/ > |
From: Piotr K. <pka...@pi...> - 2005-10-07 05:06:53
|
Jeremy White 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. > Actually some people from perlguitest group have also suggested merging those 2 modules. And don't think it is a bad idea. I have however the following concerns: 1. Who will do it? Observing the dynamics of development of Win32::GuiTest, I don't think there is much resource to do it. How does it look in your case? 2. Backward compatibility - the module is already used by some people. Saying that I do not consider points above to be major obstacles. This is definitely an idea worth consideration. Let's sleep on it. I will post your idea in our group. -- Piotr Kaluski "It is the commitment of the individuals to excellence, their mastery of the tools of their crafts, and their ability to work together that makes the product, not rules." ("Testing Computer Software" by Cem Kaner, Jack Falk, Hung Quoc Nguyen) |