From bret at pettichord.com  Mon Jan 15 12:40:01 2007
From: bret at pettichord.com (Bret Pettichord)
Date: Mon, 15 Jan 2007 11:40:01 -0600
Subject: [Wtr-development] [Wtr-general] Error with file_field in a
	modal window (using
In-Reply-To: <e26bda3e0701112201j149e7a5em640837d3b417f2df@mail.gmail.com>
References: <48851485.1168443566427.JavaMail.oqa-j2ee@openqa01.managed.contegix.com>	<45A56F9C.8010303@pettichord.com>	<e26bda3e0701102211v61e64776lc7a63cd16c7aa430@mail.gmail.com>	<45A663F3.2030809@pettichord.com>
	<e26bda3e0701112201j149e7a5em640837d3b417f2df@mail.gmail.com>
Message-ID: <45ABBC71.30500@pettichord.com>

Angrez Singh wrote:
> I'll go ahead with using "rubyw" and will make the changes to code.
> *1143* <http://svn.openqa.org/fisheye/changelog/watir?cs=1143> 
> *angrez* 	Fri, 12 January 2007, 04:03:25 -0600
> Added code for using Ruby Interpreter to execute the files for 
> clicking the Java Script dialog and entering file name in File Field 
> element.
>
> /trunk/watir/watir/winClicker.rb 
> <http://svn.openqa.org/fisheye/browse/watir/trunk/watir/watir/winClicker.rb> 
> 	1143 
> <http://svn.openqa.org/fisheye/browse/watir/trunk/watir/watir/winClicker.rb?r=1143> 
> 	(+7 -3) 	view 
> <http://svn.openqa.org/fisheye/browse/watir/trunk/watir/watir/winClicker.rb?r=1143> 
> 	diffs 
> <http://svn.openqa.org/fisheye/browse/watir/trunk/watir/watir/winClicker.rb?r1=1123&r2=1143> 
> 	 
>

Thanks for making the change.

The comments you added to the code, documenting the change should be 
included in the commit log and not the source itself. Would you please 
remove the comments from the source.

The executable code itself looks good.

Bret

From angrez at gmail.com  Tue Jan 16 04:22:46 2007
From: angrez at gmail.com (Angrez Singh)
Date: Tue, 16 Jan 2007 14:52:46 +0530
Subject: [Wtr-development] [Wtr-general] Error with file_field in a
	modal window (using
In-Reply-To: <45ABBC71.30500@pettichord.com>
References: <48851485.1168443566427.JavaMail.oqa-j2ee@openqa01.managed.contegix.com>
	<45A56F9C.8010303@pettichord.com>
	<e26bda3e0701102211v61e64776lc7a63cd16c7aa430@mail.gmail.com>
	<45A663F3.2030809@pettichord.com>
	<e26bda3e0701112201j149e7a5em640837d3b417f2df@mail.gmail.com>
	<45ABBC71.30500@pettichord.com>
Message-ID: <e26bda3e0701160122t3e533395yb28a3674ea576c5b@mail.gmail.com>

Hi Bret,

I have made the changes (removed the comments) to the file (winClicker.rb)
and commited the code.

Regards,
Angrez

On 1/15/07, Bret Pettichord <bret at pettichord.com> wrote:
>
> Angrez Singh wrote:
> > I'll go ahead with using "rubyw" and will make the changes to code.
> > *1143* <http://svn.openqa.org/fisheye/changelog/watir?cs=1143>
> > *angrez*      Fri, 12 January 2007, 04:03:25 -0600
> > Added code for using Ruby Interpreter to execute the files for
> > clicking the Java Script dialog and entering file name in File Field
> > element.
> >
> > /trunk/watir/watir/winClicker.rb
> > <
> http://svn.openqa.org/fisheye/browse/watir/trunk/watir/watir/winClicker.rb
> >
> >       1143
> > <
> http://svn.openqa.org/fisheye/browse/watir/trunk/watir/watir/winClicker.rb?r=1143
> >
> >       (+7 -3)         view
> > <
> http://svn.openqa.org/fisheye/browse/watir/trunk/watir/watir/winClicker.rb?r=1143
> >
> >       diffs
> > <
> http://svn.openqa.org/fisheye/browse/watir/trunk/watir/watir/winClicker.rb?r1=1123&r2=1143
> >
> >
> >
>
> Thanks for making the change.
>
> The comments you added to the code, documenting the change should be
> included in the commit log and not the source itself. Would you please
> remove the comments from the source.
>
> The executable code itself looks good.
>
> Bret
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://rubyforge.org/pipermail/wtr-development/attachments/20070116/41891b15/attachment.html 

From bob.cotton at rallydev.com  Wed Jan 17 16:46:57 2007
From: bob.cotton at rallydev.com (Bob Cotton)
Date: Wed, 17 Jan 2007 14:46:57 -0700
Subject: [Wtr-development] Reuniting Watir
In-Reply-To: <f96821860701171329j7ccc7f7fv9d3081efcb796752@mail.gmail.com>
	(Charley Baker's message of "Wed, 17 Jan 2007 14:29:39 -0700")
References: <ade75c5b0701161517s6cd8c81ejb5a550d7efb2b1c9@mail.gmail.com>
	<11c8704e0701170424o5d376c7ei3688bdc8737a6c33@mail.gmail.com>
	<ade75c5b0701171303l506f3c8ao8db69a047fafd99f@mail.gmail.com>
	<11c8704e0701171313v792aa357y8bb8177afa9a6094@mail.gmail.com>
	<f96821860701171329j7ccc7f7fv9d3081efcb796752@mail.gmail.com>
Message-ID: <uvchcupmilq.fsf@england.f4tech.com>


Attempting to move to wtr-development. everyone subscribed?

"Charley Baker" <charley.baker at gmail.com> writes:

> It seems as though there is a lot of interest in unifying the projects.
> II'd suggest moving this over to the dev list. Here's my breakdown of
> leads:
> Bret: Watir
> Dave: SafariWatir
> Angrez: FireWatir
> Bob: Selenium RC integration - MineralWatir
>
> Can we set up a regular weekly meeting on Skype, phone conference, irc, or
> whatever, for this project?

Weekly meetings sound like a good idea.

Bret had mentioned that this would be a post 1.5 plan. Is there a
plan for the 1.5 release?



-- 
Bob Cotton
Test Architect -- Rally Software -- rallydev.com
http://www.testarchitecture.com/blog

From bob.cotton at rallydev.com  Wed Jan 17 16:55:53 2007
From: bob.cotton at rallydev.com (Bob Cotton)
Date: Wed, 17 Jan 2007 14:55:53 -0700
Subject: [Wtr-development] Reuniting Watir
In-Reply-To: <ade75c5b0701171345r36caf09bw7620e03b7da145e7@mail.gmail.com>
	(Bret Pettichord's message of "Wed, 17 Jan 2007 15:45:22 -0600")
References: <ade75c5b0701161517s6cd8c81ejb5a550d7efb2b1c9@mail.gmail.com>
	<11c8704e0701170424o5d376c7ei3688bdc8737a6c33@mail.gmail.com>
	<ade75c5b0701171303l506f3c8ao8db69a047fafd99f@mail.gmail.com>
	<11c8704e0701171313v792aa357y8bb8177afa9a6094@mail.gmail.com>
	<f96821860701171329j7ccc7f7fv9d3081efcb796752@mail.gmail.com>
	<ade75c5b0701171345r36caf09bw7620e03b7da145e7@mail.gmail.com>
Message-ID: <uvcd55dmi6u.fsf@england.f4tech.com>

"Bret Pettichord" <bret at pettichord.com> writes:

>   Bret: Watir
>
> I suggest that we start calling this implementation Watir::IE or something
> similar, since the purpose of this discussion is to brand "Watir" as
> cross-platform cross-browser solution (or set of solutions). Other
> suggestions?

Watirie
Magellan
http://en.wikipedia.org/wiki/List_of_maritime_explorers

 -Bob

-- 
Bob Cotton
Test Architect -- Rally Software -- rallydev.com
http://www.testarchitecture.com/blog

From christopher.mcmahon at gmail.com  Wed Jan 17 17:04:51 2007
From: christopher.mcmahon at gmail.com (Chris McMahon)
Date: Wed, 17 Jan 2007 14:04:51 -0800
Subject: [Wtr-development] [Wtr-core] Reuniting Watir
In-Reply-To: <uvcd55dmi6u.fsf@england.f4tech.com>
References: <ade75c5b0701161517s6cd8c81ejb5a550d7efb2b1c9@mail.gmail.com>
	<11c8704e0701170424o5d376c7ei3688bdc8737a6c33@mail.gmail.com>
	<ade75c5b0701171303l506f3c8ao8db69a047fafd99f@mail.gmail.com>
	<11c8704e0701171313v792aa357y8bb8177afa9a6094@mail.gmail.com>
	<f96821860701171329j7ccc7f7fv9d3081efcb796752@mail.gmail.com>
	<ade75c5b0701171345r36caf09bw7620e03b7da145e7@mail.gmail.com>
	<uvcd55dmi6u.fsf@england.f4tech.com>
Message-ID: <72799cd70701171404w7305b1fcoe02e044d0f2dea7e@mail.gmail.com>

WinWatir

On 1/17/07, Bob Cotton <bob.cotton at rallydev.com> wrote:
>
> "Bret Pettichord" <bret at pettichord.com> writes:
>
> >   Bret: Watir
> >
> > I suggest that we start calling this implementation Watir::IE or
> something
> > similar, since the purpose of this discussion is to brand "Watir" as
> > cross-platform cross-browser solution (or set of solutions). Other
> > suggestions?
>
> Watirie
> Magellan
> http://en.wikipedia.org/wiki/List_of_maritime_explorers
>
> -Bob
>
> --
> Bob Cotton
> Test Architect -- Rally Software -- rallydev.com
> http://www.testarchitecture.com/blog
> _______________________________________________
> Wtr-core mailing list
> Wtr-core at rubyforge.org
> http://rubyforge.org/mailman/listinfo/wtr-core
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://rubyforge.org/pipermail/wtr-development/attachments/20070117/16901d50/attachment-0001.html 

From charley.baker at gmail.com  Wed Jan 17 17:21:16 2007
From: charley.baker at gmail.com (Charley Baker)
Date: Wed, 17 Jan 2007 15:21:16 -0700
Subject: [Wtr-development] [Wtr-core] Reuniting Watir
In-Reply-To: <72799cd70701171404w7305b1fcoe02e044d0f2dea7e@mail.gmail.com>
References: <ade75c5b0701161517s6cd8c81ejb5a550d7efb2b1c9@mail.gmail.com>
	<11c8704e0701170424o5d376c7ei3688bdc8737a6c33@mail.gmail.com>
	<ade75c5b0701171303l506f3c8ao8db69a047fafd99f@mail.gmail.com>
	<11c8704e0701171313v792aa357y8bb8177afa9a6094@mail.gmail.com>
	<f96821860701171329j7ccc7f7fv9d3081efcb796752@mail.gmail.com>
	<ade75c5b0701171345r36caf09bw7620e03b7da145e7@mail.gmail.com>
	<uvcd55dmi6u.fsf@england.f4tech.com>
	<72799cd70701171404w7305b1fcoe02e044d0f2dea7e@mail.gmail.com>
Message-ID: <f96821860701171421u2e4c4027n4d203b5ba904af2b@mail.gmail.com>

If we're doing a wrapper for Selenium. I wouldn't mind contacting and
working with the current Selenium developers and/or Paul Hammant to get him
involved.

-c

On 1/17/07, Chris McMahon <christopher.mcmahon at gmail.com> wrote:
>
>
> WinWatir
>
> On 1/17/07, Bob Cotton <bob.cotton at rallydev.com> wrote:
>
> > "Bret Pettichord" <bret at pettichord.com> writes:
> >
> > >   Bret: Watir
> > >
> > > I suggest that we start calling this implementation Watir::IE or
> > something
> > > similar, since the purpose of this discussion is to brand "Watir" as
> > > cross-platform cross-browser solution (or set of solutions). Other
> > > suggestions?
> >
> > Watirie
> > Magellan
> > http://en.wikipedia.org/wiki/List_of_maritime_explorers
> >
> > -Bob
> >
> > --
> > Bob Cotton
> > Test Architect -- Rally Software -- rallydev.com
> > http://www.testarchitecture.com/blog
> > _______________________________________________
> > Wtr-core mailing list
> > Wtr-core at rubyforge.org
> > http://rubyforge.org/mailman/listinfo/wtr-core
> >
>
>
> _______________________________________________
> Wtr-core mailing list
> Wtr-core at rubyforge.org
> http://rubyforge.org/mailman/listinfo/wtr-core
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://rubyforge.org/pipermail/wtr-development/attachments/20070117/3277746e/attachment.html 

From bret at pettichord.com  Wed Jan 17 18:55:06 2007
From: bret at pettichord.com (Bret Pettichord)
Date: Wed, 17 Jan 2007 17:55:06 -0600
Subject: [Wtr-development] [Wtr-core] Reuniting Watir
In-Reply-To: <f96821860701171421u2e4c4027n4d203b5ba904af2b@mail.gmail.com>
References: <ade75c5b0701161517s6cd8c81ejb5a550d7efb2b1c9@mail.gmail.com>
	<11c8704e0701170424o5d376c7ei3688bdc8737a6c33@mail.gmail.com>
	<ade75c5b0701171303l506f3c8ao8db69a047fafd99f@mail.gmail.com>
	<11c8704e0701171313v792aa357y8bb8177afa9a6094@mail.gmail.com>
	<f96821860701171329j7ccc7f7fv9d3081efcb796752@mail.gmail.com>
	<ade75c5b0701171345r36caf09bw7620e03b7da145e7@mail.gmail.com>
	<uvcd55dmi6u.fsf@england.f4tech.com>
	<72799cd70701171404w7305b1fcoe02e044d0f2dea7e@mail.gmail.com>
	<f96821860701171421u2e4c4027n4d203b5ba904af2b@mail.gmail.com>
Message-ID: <ade75c5b0701171555l31b879ddn8ebe36ce42fdcaa5@mail.gmail.com>

I think the next step is to start refactoring the existing Watir::IE code
base to separate the IE and Windows specific code.

Then Bob and I can start implementing the Watir::Selenium (MineralWatir)
code in the same code base.

Then we can look into pulling in the SafariWatir and FireWatir codebases.
Assuming that Angrez likes this idea. (He's been busy finising the FireWatir
1.0 release -- good for him.)

But like Bob said, I need to focus on wrapping up Watir::IE 1.5 first. I
don't think we're ready yet for a Watir 2.0 conference call.

Bret
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://rubyforge.org/pipermail/wtr-development/attachments/20070117/561ad830/attachment.html 

From angrez at gmail.com  Thu Jan 18 03:54:07 2007
From: angrez at gmail.com (Angrez Singh)
Date: Thu, 18 Jan 2007 14:24:07 +0530
Subject: [Wtr-development] [Wtr-core] Reuniting Watir
In-Reply-To: <ade75c5b0701171555l31b879ddn8ebe36ce42fdcaa5@mail.gmail.com>
References: <ade75c5b0701161517s6cd8c81ejb5a550d7efb2b1c9@mail.gmail.com>
	<11c8704e0701170424o5d376c7ei3688bdc8737a6c33@mail.gmail.com>
	<ade75c5b0701171303l506f3c8ao8db69a047fafd99f@mail.gmail.com>
	<11c8704e0701171313v792aa357y8bb8177afa9a6094@mail.gmail.com>
	<f96821860701171329j7ccc7f7fv9d3081efcb796752@mail.gmail.com>
	<ade75c5b0701171345r36caf09bw7620e03b7da145e7@mail.gmail.com>
	<uvcd55dmi6u.fsf@england.f4tech.com>
	<72799cd70701171404w7305b1fcoe02e044d0f2dea7e@mail.gmail.com>
	<f96821860701171421u2e4c4027n4d203b5ba904af2b@mail.gmail.com>
	<ade75c5b0701171555l31b879ddn8ebe36ce42fdcaa5@mail.gmail.com>
Message-ID: <e26bda3e0701180054n2ebc4d83p7e7cf472555dbe04@mail.gmail.com>

Hi all,

I just finished releasing FireWatir 1.0.1. I like the idea of merging or
reuniting the project, but need to discuss it here with the FireWatir team.
Also, its not as mature as Watir and it has its own limitations. I have the
refactored code for the Watir code base 1.4.1. But I have made a lot of
changes to that to be able to work with Firefox. Just wanted to evaluate the
effort it requires to merge the code.

Anyways, I am with the idea. Lets first refactor the WATIR::IE code and then
we can move forward.

Here's what I think:
1. Container module can be a separate module as it has nothing to do with
IE, or Firefox, or Safari.
2. We can move out the classes for HTML elements to some file, as these
classes are also browser independent.

I think this can be the starting point.

What do you say?

- Angrez


On 1/18/07, Bret Pettichord <bret at pettichord.com> wrote:
>
> I think the next step is to start refactoring the existing Watir::IE code
> base to separate the IE and Windows specific code.
>
> Then Bob and I can start implementing the Watir::Selenium (MineralWatir)
> code in the same code base.
>
> Then we can look into pulling in the SafariWatir and FireWatir codebases.
> Assuming that Angrez likes this idea. (He's been busy finising the FireWatir
> 1.0 release -- good for him.)
>
> But like Bob said, I need to focus on wrapping up Watir::IE 1.5 first. I
> don't think we're ready yet for a Watir 2.0 conference call.
>
> Bret
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://rubyforge.org/pipermail/wtr-development/attachments/20070118/05fd25a4/attachment.html 

From angrez at gmail.com  Sat Jan 20 04:29:06 2007
From: angrez at gmail.com (Angrez Singh)
Date: Sat, 20 Jan 2007 14:59:06 +0530
Subject: [Wtr-development] Fwd: Watir Unification
In-Reply-To: <7661e6730701200104u57839df5k78bf46b4a7bb27a1@mail.gmail.com>
References: <7661e6730701200104u57839df5k78bf46b4a7bb27a1@mail.gmail.com>
Message-ID: <e26bda3e0701200129k536fa153la4ad3376136d72d2@mail.gmail.com>

Hi,

Here's what Amit (owner of FireWatir & man behind the idea of FireWatir) has
to say about the unification of Watir. I would like the owner of
'wtr-development' and 'wtr-core' group to add him to the mailing list. His
e-mail id is: amit.garde at gmail.com.

0. I think unification is a good idea and I would vote for it, based
> on two primary reasons:
> -- A. I think unification (where Watir functionality is largely
> brwoser independent) is better from the point of view of end users who
> need to test on multiple browsers and platforms, because they need
> only learn Watir, and then be able to script test cases that will run
> unchanged on all the browsers and platforms of interest. This reduces
> the cost, effort, and time in building and maintaining a test suite
> for multiple browers and platforms and hence should make Watir a more
> attractive option for people who require multi-browser and platform
> support.
>
> --B More philosophically, the web application testing intention is
> conceptually separate from the specifics of the browser being used to
> test the web app, so the unification will probably support this
> philosophical perspective as well.
>
> 1. I think having a common web-application test specific API, as a
> layer that is conceptually separate from and implemented on top of
> individual browser specific layers is also a good idea. If this is
> going to be one of the results of unification, I think it is a good
> thing in itself.
>
> 2. Given issues with specific platforms and more particularly with
> differences in browser features and how easy or otherwise it is to
> implement specific web app test functionality in a given browser (for
> exanmple xpath based element searching is much easier to do with
> Firefox than with IE) the API, features, and structure of the Web app
> test layer (which will need to be supplied with concrete
> implementations by the browser specific layers) will need to be
> carefully discussed and designed.
>
> Amit


- Angrez
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://rubyforge.org/pipermail/wtr-development/attachments/20070120/45dd802b/attachment.html 

From bob.cotton at rallydev.com  Wed Jan 31 21:52:05 2007
From: bob.cotton at rallydev.com (Bob Cotton)
Date: Wed, 31 Jan 2007 19:52:05 -0700
Subject: [Wtr-development] Watir 2.0 Structure Proposal
Message-ID: <m17iv2d1yi.fsf@boblaptop.clubcotton.homeip.net>


Hey all,

Is Amit on the list yet?

After spending some time with the three code bases, original watir,
firewatir and safariwatir, I have a proposal for the structure of
Watir 2.0, that will include all these technologies plus mineralwatir
(Selenium) and any other browser driver technologies that might come
along.

This proposal is not complete, but I wanted to get it in front of
everyone to see if it holds watir :-)

1. A unified API. At AWTA, Bret and I had a discussion about the
external API for a unified Watir. We agreed that we need a single API
for all drivers. This means that some external configuration mechanism
would be necessary.

We thought API would look something like this:

      require 'watir'
      browser = Watir.create_browser
      browser.link(...).click  # etc

The same API would work for all browser drivers.

2. Dynamic configuration. Here are two approaches for dynamically
   mixing in the driver specific parts into this API:
   
   1. At "require" time
   2. Post "creation" time

  #1, at require time, would dynamically mix in the driver specific
   modules when the module was required. i.e. when Ruby first "sees"
   the code.

  #2, post "creation" time, we would create an instance of a "Browser"
   object, then mix the proper driver specific modules into *that*
   instance. This is shown in the file
   watir-2.0-skeleton/lib/watir_runtime_config.rb

  The configuration could be in an external YAML file, or parameters
  passed on the command line. An external file would work better for
  the Selenium driver, as there could be several items to configure.

  #2 has the advantage that you could have multiple instances of the
   "Browser" live at the same time, each using a browser driver.

3. Module structure:
    A suggested module structure:
    1. Watir - The top-level module

    2. Watir::BrowserDriver - The containing module for browser
       specific sub-modules, e.g.

         Watir::BrowserDriver::IEWatir (what are we calling this, BTW?)
         Watir::BrowserDriver::FireWatir
         Watir::BrowserDriver::SafariWatir
         Watir::BrowserDriver::MineralWatir

    3. Watir::BrowserDriver::XXX The module for browser specific
       code. This would be the browser specific portions of what
       resides in the Watir::IE class, or in Watir::FireWatir class.

    4. Watir::BrowserDriver::XXX::Element This module holds the driver
       specific code for the Element base class. All (most)
       sub-classes of Element should be driver neutral

4. Directory structure. See the .zip file

There is code to follow along. 

There are two .zip files.

     http://www.testarchitecture.com/watir-2.0/watir-2.0-skeleton.zip
     http://www.testarchitecture.com/watir-2.0/watir-2.0-skeleton-firewatir.zip

One with just the skeleton structure, and a WatirConfig class that
does load a YAML file and will configure the Watir module.  This code
will load and execute.

cd watir-2.0-skeleton
irb -Ilib -rwatir
Hello - This is FireWatir included into Watir::BrowserDriver
irb(main):001:0> b = Watir::Browser.new
=> #<Watir::Browser:0x5520e4>
irb(main):002:0> b.driver
=> "FireWatir"


In the other I put some of the FireWatir code (only because it was
already factored out) in this structure just as an example. IT DOES
NOT WORK.


Thoughts?

 -Bob

From bret at pettichord.com  Mon Jan 15 12:40:01 2007
From: bret at pettichord.com (Bret Pettichord)
Date: Mon, 15 Jan 2007 11:40:01 -0600
Subject: [Wtr-development] [Wtr-general] Error with file_field in a
	modal window (using
In-Reply-To: <e26bda3e0701112201j149e7a5em640837d3b417f2df@mail.gmail.com>
References: <48851485.1168443566427.JavaMail.oqa-j2ee@openqa01.managed.contegix.com>	<45A56F9C.8010303@pettichord.com>	<e26bda3e0701102211v61e64776lc7a63cd16c7aa430@mail.gmail.com>	<45A663F3.2030809@pettichord.com>
	<e26bda3e0701112201j149e7a5em640837d3b417f2df@mail.gmail.com>
Message-ID: <45ABBC71.30500@pettichord.com>

Angrez Singh wrote:
> I'll go ahead with using "rubyw" and will make the changes to code.
> *1143* <http://svn.openqa.org/fisheye/changelog/watir?cs=1143> 
> *angrez* 	Fri, 12 January 2007, 04:03:25 -0600
> Added code for using Ruby Interpreter to execute the files for 
> clicking the Java Script dialog and entering file name in File Field 
> element.
>
> /trunk/watir/watir/winClicker.rb 
> <http://svn.openqa.org/fisheye/browse/watir/trunk/watir/watir/winClicker.rb> 
> 	1143 
> <http://svn.openqa.org/fisheye/browse/watir/trunk/watir/watir/winClicker.rb?r=1143> 
> 	(+7 -3) 	view 
> <http://svn.openqa.org/fisheye/browse/watir/trunk/watir/watir/winClicker.rb?r=1143> 
> 	diffs 
> <http://svn.openqa.org/fisheye/browse/watir/trunk/watir/watir/winClicker.rb?r1=1123&r2=1143> 
> 	 
>

Thanks for making the change.

The comments you added to the code, documenting the change should be 
included in the commit log and not the source itself. Would you please 
remove the comments from the source.

The executable code itself looks good.

Bret


From angrez at gmail.com  Tue Jan 16 04:22:46 2007
From: angrez at gmail.com (Angrez Singh)
Date: Tue, 16 Jan 2007 14:52:46 +0530
Subject: [Wtr-development] [Wtr-general] Error with file_field in a
	modal window (using
In-Reply-To: <45ABBC71.30500@pettichord.com>
References: <48851485.1168443566427.JavaMail.oqa-j2ee@openqa01.managed.contegix.com>
	<45A56F9C.8010303@pettichord.com>
	<e26bda3e0701102211v61e64776lc7a63cd16c7aa430@mail.gmail.com>
	<45A663F3.2030809@pettichord.com>
	<e26bda3e0701112201j149e7a5em640837d3b417f2df@mail.gmail.com>
	<45ABBC71.30500@pettichord.com>
Message-ID: <e26bda3e0701160122t3e533395yb28a3674ea576c5b@mail.gmail.com>

Hi Bret,

I have made the changes (removed the comments) to the file (winClicker.rb)
and commited the code.

Regards,
Angrez

On 1/15/07, Bret Pettichord <bret at pettichord.com> wrote:
>
> Angrez Singh wrote:
> > I'll go ahead with using "rubyw" and will make the changes to code.
> > *1143* <http://svn.openqa.org/fisheye/changelog/watir?cs=1143>
> > *angrez*      Fri, 12 January 2007, 04:03:25 -0600
> > Added code for using Ruby Interpreter to execute the files for
> > clicking the Java Script dialog and entering file name in File Field
> > element.
> >
> > /trunk/watir/watir/winClicker.rb
> > <
> http://svn.openqa.org/fisheye/browse/watir/trunk/watir/watir/winClicker.rb
> >
> >       1143
> > <
> http://svn.openqa.org/fisheye/browse/watir/trunk/watir/watir/winClicker.rb?r=1143
> >
> >       (+7 -3)         view
> > <
> http://svn.openqa.org/fisheye/browse/watir/trunk/watir/watir/winClicker.rb?r=1143
> >
> >       diffs
> > <
> http://svn.openqa.org/fisheye/browse/watir/trunk/watir/watir/winClicker.rb?r1=1123&r2=1143
> >
> >
> >
>
> Thanks for making the change.
>
> The comments you added to the code, documenting the change should be
> included in the commit log and not the source itself. Would you please
> remove the comments from the source.
>
> The executable code itself looks good.
>
> Bret
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://rubyforge.org/pipermail/wtr-development/attachments/20070116/41891b15/attachment-0002.html>

From bob.cotton at rallydev.com  Wed Jan 17 16:46:57 2007
From: bob.cotton at rallydev.com (Bob Cotton)
Date: Wed, 17 Jan 2007 14:46:57 -0700
Subject: [Wtr-development] Reuniting Watir
In-Reply-To: <f96821860701171329j7ccc7f7fv9d3081efcb796752@mail.gmail.com>
	(Charley Baker's message of "Wed, 17 Jan 2007 14:29:39 -0700")
References: <ade75c5b0701161517s6cd8c81ejb5a550d7efb2b1c9@mail.gmail.com>
	<11c8704e0701170424o5d376c7ei3688bdc8737a6c33@mail.gmail.com>
	<ade75c5b0701171303l506f3c8ao8db69a047fafd99f@mail.gmail.com>
	<11c8704e0701171313v792aa357y8bb8177afa9a6094@mail.gmail.com>
	<f96821860701171329j7ccc7f7fv9d3081efcb796752@mail.gmail.com>
Message-ID: <uvchcupmilq.fsf@england.f4tech.com>


Attempting to move to wtr-development. everyone subscribed?

"Charley Baker" <charley.baker at gmail.com> writes:

> It seems as though there is a lot of interest in unifying the projects.
> II'd suggest moving this over to the dev list. Here's my breakdown of
> leads:
> Bret: Watir
> Dave: SafariWatir
> Angrez: FireWatir
> Bob: Selenium RC integration - MineralWatir
>
> Can we set up a regular weekly meeting on Skype, phone conference, irc, or
> whatever, for this project?

Weekly meetings sound like a good idea.

Bret had mentioned that this would be a post 1.5 plan. Is there a
plan for the 1.5 release?



-- 
Bob Cotton
Test Architect -- Rally Software -- rallydev.com
http://www.testarchitecture.com/blog


From bob.cotton at rallydev.com  Wed Jan 17 16:55:53 2007
From: bob.cotton at rallydev.com (Bob Cotton)
Date: Wed, 17 Jan 2007 14:55:53 -0700
Subject: [Wtr-development] Reuniting Watir
In-Reply-To: <ade75c5b0701171345r36caf09bw7620e03b7da145e7@mail.gmail.com>
	(Bret Pettichord's message of "Wed, 17 Jan 2007 15:45:22 -0600")
References: <ade75c5b0701161517s6cd8c81ejb5a550d7efb2b1c9@mail.gmail.com>
	<11c8704e0701170424o5d376c7ei3688bdc8737a6c33@mail.gmail.com>
	<ade75c5b0701171303l506f3c8ao8db69a047fafd99f@mail.gmail.com>
	<11c8704e0701171313v792aa357y8bb8177afa9a6094@mail.gmail.com>
	<f96821860701171329j7ccc7f7fv9d3081efcb796752@mail.gmail.com>
	<ade75c5b0701171345r36caf09bw7620e03b7da145e7@mail.gmail.com>
Message-ID: <uvcd55dmi6u.fsf@england.f4tech.com>

"Bret Pettichord" <bret at pettichord.com> writes:

>   Bret: Watir
>
> I suggest that we start calling this implementation Watir::IE or something
> similar, since the purpose of this discussion is to brand "Watir" as
> cross-platform cross-browser solution (or set of solutions). Other
> suggestions?

Watirie
Magellan
http://en.wikipedia.org/wiki/List_of_maritime_explorers

 -Bob

-- 
Bob Cotton
Test Architect -- Rally Software -- rallydev.com
http://www.testarchitecture.com/blog


From christopher.mcmahon at gmail.com  Wed Jan 17 17:04:51 2007
From: christopher.mcmahon at gmail.com (Chris McMahon)
Date: Wed, 17 Jan 2007 14:04:51 -0800
Subject: [Wtr-development] [Wtr-core] Reuniting Watir
In-Reply-To: <uvcd55dmi6u.fsf@england.f4tech.com>
References: <ade75c5b0701161517s6cd8c81ejb5a550d7efb2b1c9@mail.gmail.com>
	<11c8704e0701170424o5d376c7ei3688bdc8737a6c33@mail.gmail.com>
	<ade75c5b0701171303l506f3c8ao8db69a047fafd99f@mail.gmail.com>
	<11c8704e0701171313v792aa357y8bb8177afa9a6094@mail.gmail.com>
	<f96821860701171329j7ccc7f7fv9d3081efcb796752@mail.gmail.com>
	<ade75c5b0701171345r36caf09bw7620e03b7da145e7@mail.gmail.com>
	<uvcd55dmi6u.fsf@england.f4tech.com>
Message-ID: <72799cd70701171404w7305b1fcoe02e044d0f2dea7e@mail.gmail.com>

WinWatir

On 1/17/07, Bob Cotton <bob.cotton at rallydev.com> wrote:
>
> "Bret Pettichord" <bret at pettichord.com> writes:
>
> >   Bret: Watir
> >
> > I suggest that we start calling this implementation Watir::IE or
> something
> > similar, since the purpose of this discussion is to brand "Watir" as
> > cross-platform cross-browser solution (or set of solutions). Other
> > suggestions?
>
> Watirie
> Magellan
> http://en.wikipedia.org/wiki/List_of_maritime_explorers
>
> -Bob
>
> --
> Bob Cotton
> Test Architect -- Rally Software -- rallydev.com
> http://www.testarchitecture.com/blog
> _______________________________________________
> Wtr-core mailing list
> Wtr-core at rubyforge.org
> http://rubyforge.org/mailman/listinfo/wtr-core
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://rubyforge.org/pipermail/wtr-development/attachments/20070117/16901d50/attachment-0002.html>

From charley.baker at gmail.com  Wed Jan 17 17:21:16 2007
From: charley.baker at gmail.com (Charley Baker)
Date: Wed, 17 Jan 2007 15:21:16 -0700
Subject: [Wtr-development] [Wtr-core] Reuniting Watir
In-Reply-To: <72799cd70701171404w7305b1fcoe02e044d0f2dea7e@mail.gmail.com>
References: <ade75c5b0701161517s6cd8c81ejb5a550d7efb2b1c9@mail.gmail.com>
	<11c8704e0701170424o5d376c7ei3688bdc8737a6c33@mail.gmail.com>
	<ade75c5b0701171303l506f3c8ao8db69a047fafd99f@mail.gmail.com>
	<11c8704e0701171313v792aa357y8bb8177afa9a6094@mail.gmail.com>
	<f96821860701171329j7ccc7f7fv9d3081efcb796752@mail.gmail.com>
	<ade75c5b0701171345r36caf09bw7620e03b7da145e7@mail.gmail.com>
	<uvcd55dmi6u.fsf@england.f4tech.com>
	<72799cd70701171404w7305b1fcoe02e044d0f2dea7e@mail.gmail.com>
Message-ID: <f96821860701171421u2e4c4027n4d203b5ba904af2b@mail.gmail.com>

If we're doing a wrapper for Selenium. I wouldn't mind contacting and
working with the current Selenium developers and/or Paul Hammant to get him
involved.

-c

On 1/17/07, Chris McMahon <christopher.mcmahon at gmail.com> wrote:
>
>
> WinWatir
>
> On 1/17/07, Bob Cotton <bob.cotton at rallydev.com> wrote:
>
> > "Bret Pettichord" <bret at pettichord.com> writes:
> >
> > >   Bret: Watir
> > >
> > > I suggest that we start calling this implementation Watir::IE or
> > something
> > > similar, since the purpose of this discussion is to brand "Watir" as
> > > cross-platform cross-browser solution (or set of solutions). Other
> > > suggestions?
> >
> > Watirie
> > Magellan
> > http://en.wikipedia.org/wiki/List_of_maritime_explorers
> >
> > -Bob
> >
> > --
> > Bob Cotton
> > Test Architect -- Rally Software -- rallydev.com
> > http://www.testarchitecture.com/blog
> > _______________________________________________
> > Wtr-core mailing list
> > Wtr-core at rubyforge.org
> > http://rubyforge.org/mailman/listinfo/wtr-core
> >
>
>
> _______________________________________________
> Wtr-core mailing list
> Wtr-core at rubyforge.org
> http://rubyforge.org/mailman/listinfo/wtr-core
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://rubyforge.org/pipermail/wtr-development/attachments/20070117/3277746e/attachment-0002.html>

From bret at pettichord.com  Wed Jan 17 18:55:06 2007
From: bret at pettichord.com (Bret Pettichord)
Date: Wed, 17 Jan 2007 17:55:06 -0600
Subject: [Wtr-development] [Wtr-core] Reuniting Watir
In-Reply-To: <f96821860701171421u2e4c4027n4d203b5ba904af2b@mail.gmail.com>
References: <ade75c5b0701161517s6cd8c81ejb5a550d7efb2b1c9@mail.gmail.com>
	<11c8704e0701170424o5d376c7ei3688bdc8737a6c33@mail.gmail.com>
	<ade75c5b0701171303l506f3c8ao8db69a047fafd99f@mail.gmail.com>
	<11c8704e0701171313v792aa357y8bb8177afa9a6094@mail.gmail.com>
	<f96821860701171329j7ccc7f7fv9d3081efcb796752@mail.gmail.com>
	<ade75c5b0701171345r36caf09bw7620e03b7da145e7@mail.gmail.com>
	<uvcd55dmi6u.fsf@england.f4tech.com>
	<72799cd70701171404w7305b1fcoe02e044d0f2dea7e@mail.gmail.com>
	<f96821860701171421u2e4c4027n4d203b5ba904af2b@mail.gmail.com>
Message-ID: <ade75c5b0701171555l31b879ddn8ebe36ce42fdcaa5@mail.gmail.com>

I think the next step is to start refactoring the existing Watir::IE code
base to separate the IE and Windows specific code.

Then Bob and I can start implementing the Watir::Selenium (MineralWatir)
code in the same code base.

Then we can look into pulling in the SafariWatir and FireWatir codebases.
Assuming that Angrez likes this idea. (He's been busy finising the FireWatir
1.0 release -- good for him.)

But like Bob said, I need to focus on wrapping up Watir::IE 1.5 first. I
don't think we're ready yet for a Watir 2.0 conference call.

Bret
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://rubyforge.org/pipermail/wtr-development/attachments/20070117/561ad830/attachment-0002.html>

From angrez at gmail.com  Thu Jan 18 03:54:07 2007
From: angrez at gmail.com (Angrez Singh)
Date: Thu, 18 Jan 2007 14:24:07 +0530
Subject: [Wtr-development] [Wtr-core] Reuniting Watir
In-Reply-To: <ade75c5b0701171555l31b879ddn8ebe36ce42fdcaa5@mail.gmail.com>
References: <ade75c5b0701161517s6cd8c81ejb5a550d7efb2b1c9@mail.gmail.com>
	<11c8704e0701170424o5d376c7ei3688bdc8737a6c33@mail.gmail.com>
	<ade75c5b0701171303l506f3c8ao8db69a047fafd99f@mail.gmail.com>
	<11c8704e0701171313v792aa357y8bb8177afa9a6094@mail.gmail.com>
	<f96821860701171329j7ccc7f7fv9d3081efcb796752@mail.gmail.com>
	<ade75c5b0701171345r36caf09bw7620e03b7da145e7@mail.gmail.com>
	<uvcd55dmi6u.fsf@england.f4tech.com>
	<72799cd70701171404w7305b1fcoe02e044d0f2dea7e@mail.gmail.com>
	<f96821860701171421u2e4c4027n4d203b5ba904af2b@mail.gmail.com>
	<ade75c5b0701171555l31b879ddn8ebe36ce42fdcaa5@mail.gmail.com>
Message-ID: <e26bda3e0701180054n2ebc4d83p7e7cf472555dbe04@mail.gmail.com>

Hi all,

I just finished releasing FireWatir 1.0.1. I like the idea of merging or
reuniting the project, but need to discuss it here with the FireWatir team.
Also, its not as mature as Watir and it has its own limitations. I have the
refactored code for the Watir code base 1.4.1. But I have made a lot of
changes to that to be able to work with Firefox. Just wanted to evaluate the
effort it requires to merge the code.

Anyways, I am with the idea. Lets first refactor the WATIR::IE code and then
we can move forward.

Here's what I think:
1. Container module can be a separate module as it has nothing to do with
IE, or Firefox, or Safari.
2. We can move out the classes for HTML elements to some file, as these
classes are also browser independent.

I think this can be the starting point.

What do you say?

- Angrez


On 1/18/07, Bret Pettichord <bret at pettichord.com> wrote:
>
> I think the next step is to start refactoring the existing Watir::IE code
> base to separate the IE and Windows specific code.
>
> Then Bob and I can start implementing the Watir::Selenium (MineralWatir)
> code in the same code base.
>
> Then we can look into pulling in the SafariWatir and FireWatir codebases.
> Assuming that Angrez likes this idea. (He's been busy finising the FireWatir
> 1.0 release -- good for him.)
>
> But like Bob said, I need to focus on wrapping up Watir::IE 1.5 first. I
> don't think we're ready yet for a Watir 2.0 conference call.
>
> Bret
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://rubyforge.org/pipermail/wtr-development/attachments/20070118/05fd25a4/attachment-0002.html>

From angrez at gmail.com  Sat Jan 20 04:29:06 2007
From: angrez at gmail.com (Angrez Singh)
Date: Sat, 20 Jan 2007 14:59:06 +0530
Subject: [Wtr-development] Fwd: Watir Unification
In-Reply-To: <7661e6730701200104u57839df5k78bf46b4a7bb27a1@mail.gmail.com>
References: <7661e6730701200104u57839df5k78bf46b4a7bb27a1@mail.gmail.com>
Message-ID: <e26bda3e0701200129k536fa153la4ad3376136d72d2@mail.gmail.com>

Hi,

Here's what Amit (owner of FireWatir & man behind the idea of FireWatir) has
to say about the unification of Watir. I would like the owner of
'wtr-development' and 'wtr-core' group to add him to the mailing list. His
e-mail id is: amit.garde at gmail.com.

0. I think unification is a good idea and I would vote for it, based
> on two primary reasons:
> -- A. I think unification (where Watir functionality is largely
> brwoser independent) is better from the point of view of end users who
> need to test on multiple browsers and platforms, because they need
> only learn Watir, and then be able to script test cases that will run
> unchanged on all the browsers and platforms of interest. This reduces
> the cost, effort, and time in building and maintaining a test suite
> for multiple browers and platforms and hence should make Watir a more
> attractive option for people who require multi-browser and platform
> support.
>
> --B More philosophically, the web application testing intention is
> conceptually separate from the specifics of the browser being used to
> test the web app, so the unification will probably support this
> philosophical perspective as well.
>
> 1. I think having a common web-application test specific API, as a
> layer that is conceptually separate from and implemented on top of
> individual browser specific layers is also a good idea. If this is
> going to be one of the results of unification, I think it is a good
> thing in itself.
>
> 2. Given issues with specific platforms and more particularly with
> differences in browser features and how easy or otherwise it is to
> implement specific web app test functionality in a given browser (for
> exanmple xpath based element searching is much easier to do with
> Firefox than with IE) the API, features, and structure of the Web app
> test layer (which will need to be supplied with concrete
> implementations by the browser specific layers) will need to be
> carefully discussed and designed.
>
> Amit


- Angrez
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://rubyforge.org/pipermail/wtr-development/attachments/20070120/45dd802b/attachment-0002.html>

From bob.cotton at rallydev.com  Wed Jan 31 21:52:05 2007
From: bob.cotton at rallydev.com (Bob Cotton)
Date: Wed, 31 Jan 2007 19:52:05 -0700
Subject: [Wtr-development] Watir 2.0 Structure Proposal
Message-ID: <m17iv2d1yi.fsf@boblaptop.clubcotton.homeip.net>


Hey all,

Is Amit on the list yet?

After spending some time with the three code bases, original watir,
firewatir and safariwatir, I have a proposal for the structure of
Watir 2.0, that will include all these technologies plus mineralwatir
(Selenium) and any other browser driver technologies that might come
along.

This proposal is not complete, but I wanted to get it in front of
everyone to see if it holds watir :-)

1. A unified API. At AWTA, Bret and I had a discussion about the
external API for a unified Watir. We agreed that we need a single API
for all drivers. This means that some external configuration mechanism
would be necessary.

We thought API would look something like this:

      require 'watir'
      browser = Watir.create_browser
      browser.link(...).click  # etc

The same API would work for all browser drivers.

2. Dynamic configuration. Here are two approaches for dynamically
   mixing in the driver specific parts into this API:
   
   1. At "require" time
   2. Post "creation" time

  #1, at require time, would dynamically mix in the driver specific
   modules when the module was required. i.e. when Ruby first "sees"
   the code.

  #2, post "creation" time, we would create an instance of a "Browser"
   object, then mix the proper driver specific modules into *that*
   instance. This is shown in the file
   watir-2.0-skeleton/lib/watir_runtime_config.rb

  The configuration could be in an external YAML file, or parameters
  passed on the command line. An external file would work better for
  the Selenium driver, as there could be several items to configure.

  #2 has the advantage that you could have multiple instances of the
   "Browser" live at the same time, each using a browser driver.

3. Module structure:
    A suggested module structure:
    1. Watir - The top-level module

    2. Watir::BrowserDriver - The containing module for browser
       specific sub-modules, e.g.

         Watir::BrowserDriver::IEWatir (what are we calling this, BTW?)
         Watir::BrowserDriver::FireWatir
         Watir::BrowserDriver::SafariWatir
         Watir::BrowserDriver::MineralWatir

    3. Watir::BrowserDriver::XXX The module for browser specific
       code. This would be the browser specific portions of what
       resides in the Watir::IE class, or in Watir::FireWatir class.

    4. Watir::BrowserDriver::XXX::Element This module holds the driver
       specific code for the Element base class. All (most)
       sub-classes of Element should be driver neutral

4. Directory structure. See the .zip file

There is code to follow along. 

There are two .zip files.

     http://www.testarchitecture.com/watir-2.0/watir-2.0-skeleton.zip
     http://www.testarchitecture.com/watir-2.0/watir-2.0-skeleton-firewatir.zip

One with just the skeleton structure, and a WatirConfig class that
does load a YAML file and will configure the Watir module.  This code
will load and execute.

cd watir-2.0-skeleton
irb -Ilib -rwatir
Hello - This is FireWatir included into Watir::BrowserDriver
irb(main):001:0> b = Watir::Browser.new
=> #<Watir::Browser:0x5520e4>
irb(main):002:0> b.driver
=> "FireWatir"


In the other I put some of the FireWatir code (only because it was
already factored out) in this structure just as an example. IT DOES
NOT WORK.


Thoughts?

 -Bob


From bret at pettichord.com  Mon Jan 15 12:40:01 2007
From: bret at pettichord.com (Bret Pettichord)
Date: Mon, 15 Jan 2007 11:40:01 -0600
Subject: [Wtr-development] [Wtr-general] Error with file_field in a
	modal window (using
In-Reply-To: <e26bda3e0701112201j149e7a5em640837d3b417f2df@mail.gmail.com>
References: <48851485.1168443566427.JavaMail.oqa-j2ee@openqa01.managed.contegix.com>	<45A56F9C.8010303@pettichord.com>	<e26bda3e0701102211v61e64776lc7a63cd16c7aa430@mail.gmail.com>	<45A663F3.2030809@pettichord.com>
	<e26bda3e0701112201j149e7a5em640837d3b417f2df@mail.gmail.com>
Message-ID: <45ABBC71.30500@pettichord.com>

Angrez Singh wrote:
> I'll go ahead with using "rubyw" and will make the changes to code.
> *1143* <http://svn.openqa.org/fisheye/changelog/watir?cs=1143> 
> *angrez* 	Fri, 12 January 2007, 04:03:25 -0600
> Added code for using Ruby Interpreter to execute the files for 
> clicking the Java Script dialog and entering file name in File Field 
> element.
>
> /trunk/watir/watir/winClicker.rb 
> <http://svn.openqa.org/fisheye/browse/watir/trunk/watir/watir/winClicker.rb> 
> 	1143 
> <http://svn.openqa.org/fisheye/browse/watir/trunk/watir/watir/winClicker.rb?r=1143> 
> 	(+7 -3) 	view 
> <http://svn.openqa.org/fisheye/browse/watir/trunk/watir/watir/winClicker.rb?r=1143> 
> 	diffs 
> <http://svn.openqa.org/fisheye/browse/watir/trunk/watir/watir/winClicker.rb?r1=1123&r2=1143> 
> 	 
>

Thanks for making the change.

The comments you added to the code, documenting the change should be 
included in the commit log and not the source itself. Would you please 
remove the comments from the source.

The executable code itself looks good.

Bret


From angrez at gmail.com  Tue Jan 16 04:22:46 2007
From: angrez at gmail.com (Angrez Singh)
Date: Tue, 16 Jan 2007 14:52:46 +0530
Subject: [Wtr-development] [Wtr-general] Error with file_field in a
	modal window (using
In-Reply-To: <45ABBC71.30500@pettichord.com>
References: <48851485.1168443566427.JavaMail.oqa-j2ee@openqa01.managed.contegix.com>
	<45A56F9C.8010303@pettichord.com>
	<e26bda3e0701102211v61e64776lc7a63cd16c7aa430@mail.gmail.com>
	<45A663F3.2030809@pettichord.com>
	<e26bda3e0701112201j149e7a5em640837d3b417f2df@mail.gmail.com>
	<45ABBC71.30500@pettichord.com>
Message-ID: <e26bda3e0701160122t3e533395yb28a3674ea576c5b@mail.gmail.com>

Hi Bret,

I have made the changes (removed the comments) to the file (winClicker.rb)
and commited the code.

Regards,
Angrez

On 1/15/07, Bret Pettichord <bret at pettichord.com> wrote:
>
> Angrez Singh wrote:
> > I'll go ahead with using "rubyw" and will make the changes to code.
> > *1143* <http://svn.openqa.org/fisheye/changelog/watir?cs=1143>
> > *angrez*      Fri, 12 January 2007, 04:03:25 -0600
> > Added code for using Ruby Interpreter to execute the files for
> > clicking the Java Script dialog and entering file name in File Field
> > element.
> >
> > /trunk/watir/watir/winClicker.rb
> > <
> http://svn.openqa.org/fisheye/browse/watir/trunk/watir/watir/winClicker.rb
> >
> >       1143
> > <
> http://svn.openqa.org/fisheye/browse/watir/trunk/watir/watir/winClicker.rb?r=1143
> >
> >       (+7 -3)         view
> > <
> http://svn.openqa.org/fisheye/browse/watir/trunk/watir/watir/winClicker.rb?r=1143
> >
> >       diffs
> > <
> http://svn.openqa.org/fisheye/browse/watir/trunk/watir/watir/winClicker.rb?r1=1123&r2=1143
> >
> >
> >
>
> Thanks for making the change.
>
> The comments you added to the code, documenting the change should be
> included in the commit log and not the source itself. Would you please
> remove the comments from the source.
>
> The executable code itself looks good.
>
> Bret
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://rubyforge.org/pipermail/wtr-development/attachments/20070116/41891b15/attachment-0003.html>

From bob.cotton at rallydev.com  Wed Jan 17 16:46:57 2007
From: bob.cotton at rallydev.com (Bob Cotton)
Date: Wed, 17 Jan 2007 14:46:57 -0700
Subject: [Wtr-development] Reuniting Watir
In-Reply-To: <f96821860701171329j7ccc7f7fv9d3081efcb796752@mail.gmail.com>
	(Charley Baker's message of "Wed, 17 Jan 2007 14:29:39 -0700")
References: <ade75c5b0701161517s6cd8c81ejb5a550d7efb2b1c9@mail.gmail.com>
	<11c8704e0701170424o5d376c7ei3688bdc8737a6c33@mail.gmail.com>
	<ade75c5b0701171303l506f3c8ao8db69a047fafd99f@mail.gmail.com>
	<11c8704e0701171313v792aa357y8bb8177afa9a6094@mail.gmail.com>
	<f96821860701171329j7ccc7f7fv9d3081efcb796752@mail.gmail.com>
Message-ID: <uvchcupmilq.fsf@england.f4tech.com>


Attempting to move to wtr-development. everyone subscribed?

"Charley Baker" <charley.baker at gmail.com> writes:

> It seems as though there is a lot of interest in unifying the projects.
> II'd suggest moving this over to the dev list. Here's my breakdown of
> leads:
> Bret: Watir
> Dave: SafariWatir
> Angrez: FireWatir
> Bob: Selenium RC integration - MineralWatir
>
> Can we set up a regular weekly meeting on Skype, phone conference, irc, or
> whatever, for this project?

Weekly meetings sound like a good idea.

Bret had mentioned that this would be a post 1.5 plan. Is there a
plan for the 1.5 release?



-- 
Bob Cotton
Test Architect -- Rally Software -- rallydev.com
http://www.testarchitecture.com/blog


From bob.cotton at rallydev.com  Wed Jan 17 16:55:53 2007
From: bob.cotton at rallydev.com (Bob Cotton)
Date: Wed, 17 Jan 2007 14:55:53 -0700
Subject: [Wtr-development] Reuniting Watir
In-Reply-To: <ade75c5b0701171345r36caf09bw7620e03b7da145e7@mail.gmail.com>
	(Bret Pettichord's message of "Wed, 17 Jan 2007 15:45:22 -0600")
References: <ade75c5b0701161517s6cd8c81ejb5a550d7efb2b1c9@mail.gmail.com>
	<11c8704e0701170424o5d376c7ei3688bdc8737a6c33@mail.gmail.com>
	<ade75c5b0701171303l506f3c8ao8db69a047fafd99f@mail.gmail.com>
	<11c8704e0701171313v792aa357y8bb8177afa9a6094@mail.gmail.com>
	<f96821860701171329j7ccc7f7fv9d3081efcb796752@mail.gmail.com>
	<ade75c5b0701171345r36caf09bw7620e03b7da145e7@mail.gmail.com>
Message-ID: <uvcd55dmi6u.fsf@england.f4tech.com>

"Bret Pettichord" <bret at pettichord.com> writes:

>   Bret: Watir
>
> I suggest that we start calling this implementation Watir::IE or something
> similar, since the purpose of this discussion is to brand "Watir" as
> cross-platform cross-browser solution (or set of solutions). Other
> suggestions?

Watirie
Magellan
http://en.wikipedia.org/wiki/List_of_maritime_explorers

 -Bob

-- 
Bob Cotton
Test Architect -- Rally Software -- rallydev.com
http://www.testarchitecture.com/blog


From christopher.mcmahon at gmail.com  Wed Jan 17 17:04:51 2007
From: christopher.mcmahon at gmail.com (Chris McMahon)
Date: Wed, 17 Jan 2007 14:04:51 -0800
Subject: [Wtr-development] [Wtr-core] Reuniting Watir
In-Reply-To: <uvcd55dmi6u.fsf@england.f4tech.com>
References: <ade75c5b0701161517s6cd8c81ejb5a550d7efb2b1c9@mail.gmail.com>
	<11c8704e0701170424o5d376c7ei3688bdc8737a6c33@mail.gmail.com>
	<ade75c5b0701171303l506f3c8ao8db69a047fafd99f@mail.gmail.com>
	<11c8704e0701171313v792aa357y8bb8177afa9a6094@mail.gmail.com>
	<f96821860701171329j7ccc7f7fv9d3081efcb796752@mail.gmail.com>
	<ade75c5b0701171345r36caf09bw7620e03b7da145e7@mail.gmail.com>
	<uvcd55dmi6u.fsf@england.f4tech.com>
Message-ID: <72799cd70701171404w7305b1fcoe02e044d0f2dea7e@mail.gmail.com>

WinWatir

On 1/17/07, Bob Cotton <bob.cotton at rallydev.com> wrote:
>
> "Bret Pettichord" <bret at pettichord.com> writes:
>
> >   Bret: Watir
> >
> > I suggest that we start calling this implementation Watir::IE or
> something
> > similar, since the purpose of this discussion is to brand "Watir" as
> > cross-platform cross-browser solution (or set of solutions). Other
> > suggestions?
>
> Watirie
> Magellan
> http://en.wikipedia.org/wiki/List_of_maritime_explorers
>
> -Bob
>
> --
> Bob Cotton
> Test Architect -- Rally Software -- rallydev.com
> http://www.testarchitecture.com/blog
> _______________________________________________
> Wtr-core mailing list
> Wtr-core at rubyforge.org
> http://rubyforge.org/mailman/listinfo/wtr-core
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://rubyforge.org/pipermail/wtr-development/attachments/20070117/16901d50/attachment-0003.html>

From charley.baker at gmail.com  Wed Jan 17 17:21:16 2007
From: charley.baker at gmail.com (Charley Baker)
Date: Wed, 17 Jan 2007 15:21:16 -0700
Subject: [Wtr-development] [Wtr-core] Reuniting Watir
In-Reply-To: <72799cd70701171404w7305b1fcoe02e044d0f2dea7e@mail.gmail.com>
References: <ade75c5b0701161517s6cd8c81ejb5a550d7efb2b1c9@mail.gmail.com>
	<11c8704e0701170424o5d376c7ei3688bdc8737a6c33@mail.gmail.com>
	<ade75c5b0701171303l506f3c8ao8db69a047fafd99f@mail.gmail.com>
	<11c8704e0701171313v792aa357y8bb8177afa9a6094@mail.gmail.com>
	<f96821860701171329j7ccc7f7fv9d3081efcb796752@mail.gmail.com>
	<ade75c5b0701171345r36caf09bw7620e03b7da145e7@mail.gmail.com>
	<uvcd55dmi6u.fsf@england.f4tech.com>
	<72799cd70701171404w7305b1fcoe02e044d0f2dea7e@mail.gmail.com>
Message-ID: <f96821860701171421u2e4c4027n4d203b5ba904af2b@mail.gmail.com>

If we're doing a wrapper for Selenium. I wouldn't mind contacting and
working with the current Selenium developers and/or Paul Hammant to get him
involved.

-c

On 1/17/07, Chris McMahon <christopher.mcmahon at gmail.com> wrote:
>
>
> WinWatir
>
> On 1/17/07, Bob Cotton <bob.cotton at rallydev.com> wrote:
>
> > "Bret Pettichord" <bret at pettichord.com> writes:
> >
> > >   Bret: Watir
> > >
> > > I suggest that we start calling this implementation Watir::IE or
> > something
> > > similar, since the purpose of this discussion is to brand "Watir" as
> > > cross-platform cross-browser solution (or set of solutions). Other
> > > suggestions?
> >
> > Watirie
> > Magellan
> > http://en.wikipedia.org/wiki/List_of_maritime_explorers
> >
> > -Bob
> >
> > --
> > Bob Cotton
> > Test Architect -- Rally Software -- rallydev.com
> > http://www.testarchitecture.com/blog
> > _______________________________________________
> > Wtr-core mailing list
> > Wtr-core at rubyforge.org
> > http://rubyforge.org/mailman/listinfo/wtr-core
> >
>
>
> _______________________________________________
> Wtr-core mailing list
> Wtr-core at rubyforge.org
> http://rubyforge.org/mailman/listinfo/wtr-core
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://rubyforge.org/pipermail/wtr-development/attachments/20070117/3277746e/attachment-0003.html>

From bret at pettichord.com  Wed Jan 17 18:55:06 2007
From: bret at pettichord.com (Bret Pettichord)
Date: Wed, 17 Jan 2007 17:55:06 -0600
Subject: [Wtr-development] [Wtr-core] Reuniting Watir
In-Reply-To: <f96821860701171421u2e4c4027n4d203b5ba904af2b@mail.gmail.com>
References: <ade75c5b0701161517s6cd8c81ejb5a550d7efb2b1c9@mail.gmail.com>
	<11c8704e0701170424o5d376c7ei3688bdc8737a6c33@mail.gmail.com>
	<ade75c5b0701171303l506f3c8ao8db69a047fafd99f@mail.gmail.com>
	<11c8704e0701171313v792aa357y8bb8177afa9a6094@mail.gmail.com>
	<f96821860701171329j7ccc7f7fv9d3081efcb796752@mail.gmail.com>
	<ade75c5b0701171345r36caf09bw7620e03b7da145e7@mail.gmail.com>
	<uvcd55dmi6u.fsf@england.f4tech.com>
	<72799cd70701171404w7305b1fcoe02e044d0f2dea7e@mail.gmail.com>
	<f96821860701171421u2e4c4027n4d203b5ba904af2b@mail.gmail.com>
Message-ID: <ade75c5b0701171555l31b879ddn8ebe36ce42fdcaa5@mail.gmail.com>

I think the next step is to start refactoring the existing Watir::IE code
base to separate the IE and Windows specific code.

Then Bob and I can start implementing the Watir::Selenium (MineralWatir)
code in the same code base.

Then we can look into pulling in the SafariWatir and FireWatir codebases.
Assuming that Angrez likes this idea. (He's been busy finising the FireWatir
1.0 release -- good for him.)

But like Bob said, I need to focus on wrapping up Watir::IE 1.5 first. I
don't think we're ready yet for a Watir 2.0 conference call.

Bret
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://rubyforge.org/pipermail/wtr-development/attachments/20070117/561ad830/attachment-0003.html>

From angrez at gmail.com  Thu Jan 18 03:54:07 2007
From: angrez at gmail.com (Angrez Singh)
Date: Thu, 18 Jan 2007 14:24:07 +0530
Subject: [Wtr-development] [Wtr-core] Reuniting Watir
In-Reply-To: <ade75c5b0701171555l31b879ddn8ebe36ce42fdcaa5@mail.gmail.com>
References: <ade75c5b0701161517s6cd8c81ejb5a550d7efb2b1c9@mail.gmail.com>
	<11c8704e0701170424o5d376c7ei3688bdc8737a6c33@mail.gmail.com>
	<ade75c5b0701171303l506f3c8ao8db69a047fafd99f@mail.gmail.com>
	<11c8704e0701171313v792aa357y8bb8177afa9a6094@mail.gmail.com>
	<f96821860701171329j7ccc7f7fv9d3081efcb796752@mail.gmail.com>
	<ade75c5b0701171345r36caf09bw7620e03b7da145e7@mail.gmail.com>
	<uvcd55dmi6u.fsf@england.f4tech.com>
	<72799cd70701171404w7305b1fcoe02e044d0f2dea7e@mail.gmail.com>
	<f96821860701171421u2e4c4027n4d203b5ba904af2b@mail.gmail.com>
	<ade75c5b0701171555l31b879ddn8ebe36ce42fdcaa5@mail.gmail.com>
Message-ID: <e26bda3e0701180054n2ebc4d83p7e7cf472555dbe04@mail.gmail.com>

Hi all,

I just finished releasing FireWatir 1.0.1. I like the idea of merging or
reuniting the project, but need to discuss it here with the FireWatir team.
Also, its not as mature as Watir and it has its own limitations. I have the
refactored code for the Watir code base 1.4.1. But I have made a lot of
changes to that to be able to work with Firefox. Just wanted to evaluate the
effort it requires to merge the code.

Anyways, I am with the idea. Lets first refactor the WATIR::IE code and then
we can move forward.

Here's what I think:
1. Container module can be a separate module as it has nothing to do with
IE, or Firefox, or Safari.
2. We can move out the classes for HTML elements to some file, as these
classes are also browser independent.

I think this can be the starting point.

What do you say?

- Angrez


On 1/18/07, Bret Pettichord <bret at pettichord.com> wrote:
>
> I think the next step is to start refactoring the existing Watir::IE code
> base to separate the IE and Windows specific code.
>
> Then Bob and I can start implementing the Watir::Selenium (MineralWatir)
> code in the same code base.
>
> Then we can look into pulling in the SafariWatir and FireWatir codebases.
> Assuming that Angrez likes this idea. (He's been busy finising the FireWatir
> 1.0 release -- good for him.)
>
> But like Bob said, I need to focus on wrapping up Watir::IE 1.5 first. I
> don't think we're ready yet for a Watir 2.0 conference call.
>
> Bret
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://rubyforge.org/pipermail/wtr-development/attachments/20070118/05fd25a4/attachment-0003.html>

From angrez at gmail.com  Sat Jan 20 04:29:06 2007
From: angrez at gmail.com (Angrez Singh)
Date: Sat, 20 Jan 2007 14:59:06 +0530
Subject: [Wtr-development] Fwd: Watir Unification
In-Reply-To: <7661e6730701200104u57839df5k78bf46b4a7bb27a1@mail.gmail.com>
References: <7661e6730701200104u57839df5k78bf46b4a7bb27a1@mail.gmail.com>
Message-ID: <e26bda3e0701200129k536fa153la4ad3376136d72d2@mail.gmail.com>

Hi,

Here's what Amit (owner of FireWatir & man behind the idea of FireWatir) has
to say about the unification of Watir. I would like the owner of
'wtr-development' and 'wtr-core' group to add him to the mailing list. His
e-mail id is: amit.garde at gmail.com.

0. I think unification is a good idea and I would vote for it, based
> on two primary reasons:
> -- A. I think unification (where Watir functionality is largely
> brwoser independent) is better from the point of view of end users who
> need to test on multiple browsers and platforms, because they need
> only learn Watir, and then be able to script test cases that will run
> unchanged on all the browsers and platforms of interest. This reduces
> the cost, effort, and time in building and maintaining a test suite
> for multiple browers and platforms and hence should make Watir a more
> attractive option for people who require multi-browser and platform
> support.
>
> --B More philosophically, the web application testing intention is
> conceptually separate from the specifics of the browser being used to
> test the web app, so the unification will probably support this
> philosophical perspective as well.
>
> 1. I think having a common web-application test specific API, as a
> layer that is conceptually separate from and implemented on top of
> individual browser specific layers is also a good idea. If this is
> going to be one of the results of unification, I think it is a good
> thing in itself.
>
> 2. Given issues with specific platforms and more particularly with
> differences in browser features and how easy or otherwise it is to
> implement specific web app test functionality in a given browser (for
> exanmple xpath based element searching is much easier to do with
> Firefox than with IE) the API, features, and structure of the Web app
> test layer (which will need to be supplied with concrete
> implementations by the browser specific layers) will need to be
> carefully discussed and designed.
>
> Amit


- Angrez
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://rubyforge.org/pipermail/wtr-development/attachments/20070120/45dd802b/attachment-0003.html>

From bob.cotton at rallydev.com  Wed Jan 31 21:52:05 2007
From: bob.cotton at rallydev.com (Bob Cotton)
Date: Wed, 31 Jan 2007 19:52:05 -0700
Subject: [Wtr-development] Watir 2.0 Structure Proposal
Message-ID: <m17iv2d1yi.fsf@boblaptop.clubcotton.homeip.net>


Hey all,

Is Amit on the list yet?

After spending some time with the three code bases, original watir,
firewatir and safariwatir, I have a proposal for the structure of
Watir 2.0, that will include all these technologies plus mineralwatir
(Selenium) and any other browser driver technologies that might come
along.

This proposal is not complete, but I wanted to get it in front of
everyone to see if it holds watir :-)

1. A unified API. At AWTA, Bret and I had a discussion about the
external API for a unified Watir. We agreed that we need a single API
for all drivers. This means that some external configuration mechanism
would be necessary.

We thought API would look something like this:

      require 'watir'
      browser = Watir.create_browser
      browser.link(...).click  # etc

The same API would work for all browser drivers.

2. Dynamic configuration. Here are two approaches for dynamically
   mixing in the driver specific parts into this API:
   
   1. At "require" time
   2. Post "creation" time

  #1, at require time, would dynamically mix in the driver specific
   modules when the module was required. i.e. when Ruby first "sees"
   the code.

  #2, post "creation" time, we would create an instance of a "Browser"
   object, then mix the proper driver specific modules into *that*
   instance. This is shown in the file
   watir-2.0-skeleton/lib/watir_runtime_config.rb

  The configuration could be in an external YAML file, or parameters
  passed on the command line. An external file would work better for
  the Selenium driver, as there could be several items to configure.

  #2 has the advantage that you could have multiple instances of the
   "Browser" live at the same time, each using a browser driver.

3. Module structure:
    A suggested module structure:
    1. Watir - The top-level module

    2. Watir::BrowserDriver - The containing module for browser
       specific sub-modules, e.g.

         Watir::BrowserDriver::IEWatir (what are we calling this, BTW?)
         Watir::BrowserDriver::FireWatir
         Watir::BrowserDriver::SafariWatir
         Watir::BrowserDriver::MineralWatir

    3. Watir::BrowserDriver::XXX The module for browser specific
       code. This would be the browser specific portions of what
       resides in the Watir::IE class, or in Watir::FireWatir class.

    4. Watir::BrowserDriver::XXX::Element This module holds the driver
       specific code for the Element base class. All (most)
       sub-classes of Element should be driver neutral

4. Directory structure. See the .zip file

There is code to follow along. 

There are two .zip files.

     http://www.testarchitecture.com/watir-2.0/watir-2.0-skeleton.zip
     http://www.testarchitecture.com/watir-2.0/watir-2.0-skeleton-firewatir.zip

One with just the skeleton structure, and a WatirConfig class that
does load a YAML file and will configure the Watir module.  This code
will load and execute.

cd watir-2.0-skeleton
irb -Ilib -rwatir
Hello - This is FireWatir included into Watir::BrowserDriver
irb(main):001:0> b = Watir::Browser.new
=> #<Watir::Browser:0x5520e4>
irb(main):002:0> b.driver
=> "FireWatir"


In the other I put some of the FireWatir code (only because it was
already factored out) in this structure just as an example. IT DOES
NOT WORK.


Thoughts?

 -Bob