I would love to add them to the core, however there is no way I can
do this, since I am not a member of winguitest project on source
forge. Of course, I can place distribution somewhere else, and link
to them from the Win32::GuiTest documentation but it would lead to
I fully agree that compatibility, ease of use and so on are
important. And I had that in mind while implementing my functions. In
most projects the next step should be a peer review and discussion of
the code. However, we don't have time and resources to do that. We
have to choose between 2 evils
* Let unsufficiently discussed changes go into the core and let the
module to become richer
* Wait with all new changes until we have time to review them, which
considering current resources would stop the development.
I think the first option is better.
And congratulations for your son! Is this your first child?
Well, I expect that your activity in this group will drop
significantly :-)). I know something about it, because I have 2 kids.
--- In email@example.com
, "Dennis K. Paulsen"
> Hello Piotr,
> Feel free to implement these changes in the core if you find the
> time. No one will know the changes better then yourself. :-) As
> know and as good development practice suggests, we just need to
> think about level of compatibility, ease-of-use, standardization,
> etc, etc.
> My current employment consumes the majority of time, in addition to
> my new son, otherwise I would be more inclined to merge these
> changes myself. :-)
> --- In firstname.lastname@example.org, "Piotr Kaluski" <pkaluski@p...>
> > Hi,
> > I have added new tutorial to win32::guitest documentation. The
> > documentation can be found here ->
> > http://www.piotrkaluski.com/files/winguitest/docs/index.html (as
> > usuall). The new tutorial starts in section "Going further" in
> > "2. GUI Testing - tutorial".
> > This new tutorial deals with automation of more advanced
> > describes new functions, which are not included in the standard
> > distribution (1.50.3-ad) so I included an installation package
> > those new functions in the tutorial.
> > Dennis and Gabor - I insist that those functions are included in
> > next distribution, unless you find a serious bug in them. The
> > development of Win32::GuiTest goes really slowly (which is
> > fault - we all work on it in our free time) therefore we should
> > users in testing new functionalities as early as possible. We can
> > those new function to be experimental (as suggested by Gabor,
> which I
> > think is a good idea) but we should not postpone including new
> > until we think it over 5 times because we don't have resources
> > For the same reason I insist on adding functions from my post 876
> > 885. Should you need any further assistance in doing this - let
> > Should you have any comments on my new tutorial - let me know.
> > -Piotr