From bret at pettichord.com Tue Apr 29 20:27:29 2008 From: bret at pettichord.com (Bret Pettichord) Date: Tue, 29 Apr 2008 19:27:29 -0500 Subject: [Wtr-development] Integrating Watir and FireWatir Message-ID: Last November I wrote a report comparing Watir to FireWatir and laying out a plan forward for integrating the code bases. http://www.io.com/~wazmo/blog/archives/2007_11.html#000263 With one big exception, I still stand by this report and plan. In the report I expressed concern about FireWatir's dependency on JSSH, but I'm longer am worried about this. I've since learned that JSSH is in fact being maintained by the Mozilla project and that you can compile it and use it without problem with FireFox 3. In that report, I also blanched at the effort of getting the code bases in sync again. I still think it's a big effort, but with funding for Watir this now seems much less daunting. In fact, I think its the most important thing we need if we are going to grow the Watir community. In that report, I mostly focussed on the code bases themselves, but part of the challenge is also in pulling together the infrastructure for the projects. I recently spoke with Angrez Singh and we agreed to work out the details of a migration plan here. SVN. I want to have the Watir and FireWatir codebases in a single repository. Currently Watir is hosted at OpenQA.org and FireWatir is hosted at GoogleCode. Putting them into single repository is the only way that I know for allow us to safely remove duplications with a single commit. Part of the problem right now is simply that we have three slightly different versions of the FireWatir codebase itself: the official repo at googlecode, a copy with a few fixes to the testsuite in the vendor directory of the Watir codebase, and a private version that Paul Rogers has been applying patches to. So we need to get this sorted out too. Tests. As mentioned in the November report, I think we need to start by merging our test suites, so that we have a single suite that allows individual tests to be instrumented as applying to IE or Firefox or both. That way we won't have test duplication and can verify that the implementations have the same behavior. Gems. I just uploaded the FireWatir gem to the Rubyforge. Now you can just do a "gem install firewatir" without first downloading the gem from Google Code. Overall, our plan is to eventually migrate both projects to Watir.com, a new site that will host all Watir-related projects. I'd eventually like to see us pull together all the material from Google Code (FireWatir) and OpenQA (Watir). We'd also like to move the website from wtr.rubyforge.org, although Rubyforge may continue to be the best place to distribute gems from. Anyway, before I go into further details, I'm sure there are questions about this. Ask away! Bret -- Bret Pettichord CTO, WatirCraft LLC Lead Developer, Watir, http://wtr.rubyforge.org Blog (Essays), http://www.io.com/~wazmo/blog MiniBlog (Links), http://feeds.feedburner.com/bretshotlist -------------- next part -------------- An HTML attachment was scrubbed... URL: From paul.rogers at shaw.ca Tue Apr 29 23:07:48 2008 From: paul.rogers at shaw.ca (Paul Rogers) Date: Tue, 29 Apr 2008 21:07:48 -0600 Subject: [Wtr-development] Integrating Watir and FireWatir In-Reply-To: References: Message-ID: there are also some good patches flying around too. I cant remember where they are right now but they include - patch to get multiple browsers running, patch to speed up the start up process, and Ive got a patch that makes the start up a bit better, but I cant remember why mine is different right now (possibly it better supports mac and win). Paul On Tue, Apr 29, 2008 at 6:27 PM, Bret Pettichord wrote: > Last November I wrote a report comparing Watir to FireWatir and laying > out a plan forward for integrating the code bases. > > http://www.io.com/~wazmo/blog/archives/2007_11.html#000263 > > With one big exception, I still stand by this report and plan. In the > report I expressed concern about FireWatir's dependency on JSSH, but > I'm longer am worried about this. I've since learned that JSSH is in > fact being maintained by the Mozilla project and that you can compile > it and use it without problem with FireFox 3. > > In that report, I also blanched at the effort of getting the code > bases in sync again. I still think it's a big effort, but with funding > for Watir this now seems much less daunting. In fact, I think its the > most important thing we need if we are going to grow the Watir > community. > > In that report, I mostly focussed on the code bases themselves, but > part of the challenge is also in pulling together the infrastructure > for the projects. I recently spoke with Angrez Singh and we agreed to > work out the details of a migration plan here. > > SVN. I want to have the Watir and FireWatir codebases in a single > repository. Currently Watir is hosted at OpenQA.org and FireWatir is > hosted at GoogleCode. Putting them into single repository is the only > way that I know for allow us to safely remove duplications with a > single commit. Part of the problem right now is simply that we have > three slightly different versions of the FireWatir codebase itself: > the official repo at googlecode, a copy with a few fixes to the > testsuite in the vendor directory of the Watir codebase, and a private > version that Paul Rogers has been applying patches to. So we need to > get this sorted out too. > > Tests. As mentioned in the November report, I think we need to start > by merging our test suites, so that we have a single suite that allows > individual tests to be instrumented as applying to IE or Firefox or > both. That way we won't have test duplication and can verify that the > implementations have the same behavior. > > Gems. I just uploaded the FireWatir gem to the Rubyforge. Now you can > just do a "gem install firewatir" without first downloading the gem > from Google Code. > > Overall, our plan is to eventually migrate both projects to Watir.com, > a new site that will host all Watir-related projects. I'd eventually > like to see us pull together all the material from Google Code > (FireWatir) and OpenQA (Watir). We'd also like to move the website > from wtr.rubyforge.org, although Rubyforge may continue to be the best > place to distribute gems from. > > Anyway, before I go into further details, I'm sure there are questions > about this. Ask away! > > Bret > > -- > Bret Pettichord > CTO, WatirCraft LLC > Lead Developer, Watir, http://wtr.rubyforge.org > Blog (Essays), http://www.io.com/~wazmo/blog > MiniBlog (Links), http://feeds.feedburner.com/bretshotlist > _______________________________________________ > Wtr-development mailing list > Wtr-development at rubyforge.org > http://rubyforge.org/mailman/listinfo/wtr-development > From bret at pettichord.com Wed Apr 30 15:01:16 2008 From: bret at pettichord.com (Bret Pettichord) Date: Wed, 30 Apr 2008 14:01:16 -0500 Subject: [Wtr-development] Integrating Watir and FireWatir In-Reply-To: References: Message-ID: > > and Ive got > a patch that makes the start up a bit better, but I cant remember why > mine is different right now (possibly it better supports mac and win). Paul, could you please send us this patch. Bret -------------- next part -------------- An HTML attachment was scrubbed... URL: From bret at pettichord.com Wed Apr 30 15:02:49 2008 From: bret at pettichord.com (Bret Pettichord) Date: Wed, 30 Apr 2008 14:02:49 -0500 Subject: [Wtr-development] Integrating Watir and FireWatir In-Reply-To: References: Message-ID: Angrez, Amit, Could you all please comment on this plan before i go into further elaboration. I'm not even sure if you are reading this list. What do others think about this plan? Bret On Tue, Apr 29, 2008 at 7:27 PM, Bret Pettichord wrote: > Last November I wrote a report comparing Watir to FireWatir and laying > out a plan forward for integrating the code bases. > > http://www.io.com/~wazmo/blog/archives/2007_11.html#000263 > > With one big exception, I still stand by this report and plan. In the > report I expressed concern about FireWatir's dependency on JSSH, but > I'm longer am worried about this. I've since learned that JSSH is in > fact being maintained by the Mozilla project and that you can compile > it and use it without problem with FireFox 3. > > In that report, I also blanched at the effort of getting the code > bases in sync again. I still think it's a big effort, but with funding > for Watir this now seems much less daunting. In fact, I think its the > most important thing we need if we are going to grow the Watir > community. > > In that report, I mostly focussed on the code bases themselves, but > part of the challenge is also in pulling together the infrastructure > for the projects. I recently spoke with Angrez Singh and we agreed to > work out the details of a migration plan here. > > SVN. I want to have the Watir and FireWatir codebases in a single > repository. Currently Watir is hosted at OpenQA.org and FireWatir is > hosted at GoogleCode. Putting them into single repository is the only > way that I know for allow us to safely remove duplications with a > single commit. Part of the problem right now is simply that we have > three slightly different versions of the FireWatir codebase itself: > the official repo at googlecode, a copy with a few fixes to the > testsuite in the vendor directory of the Watir codebase, and a private > version that Paul Rogers has been applying patches to. So we need to > get this sorted out too. > > Tests. As mentioned in the November report, I think we need to start > by merging our test suites, so that we have a single suite that allows > individual tests to be instrumented as applying to IE or Firefox or > both. That way we won't have test duplication and can verify that the > implementations have the same behavior. > > Gems. I just uploaded the FireWatir gem to the Rubyforge. Now you can > just do a "gem install firewatir" without first downloading the gem > from Google Code. > > Overall, our plan is to eventually migrate both projects to Watir.com, > a new site that will host all Watir-related projects. I'd eventually > like to see us pull together all the material from Google Code > (FireWatir) and OpenQA (Watir). We'd also like to move the website > from wtr.rubyforge.org, although Rubyforge may continue to be the best > place to distribute gems from. > > Anyway, before I go into further details, I'm sure there are questions > about this. Ask away! > > Bret > > -- > Bret Pettichord > CTO, WatirCraft LLC > Lead Developer, Watir, http://wtr.rubyforge.org > Blog (Essays), http://www.io.com/~wazmo/blog > MiniBlog (Links), http://feeds.feedburner.com/bretshotlist -- Bret Pettichord CTO, WatirCraft LLC Lead Developer, Watir, http://wtr.rubyforge.org Blog (Essays), http://www.io.com/~wazmo/blog MiniBlog (Links), http://feeds.feedburner.com/bretshotlist -------------- next part -------------- An HTML attachment was scrubbed... URL: From paul.rogers at shaw.ca Wed Apr 30 15:18:23 2008 From: paul.rogers at shaw.ca (Paul Rogers) Date: Wed, 30 Apr 2008 13:18:23 -0600 Subject: [Wtr-development] Integrating Watir and FireWatir In-Reply-To: References: Message-ID: what format would you like? I guess the first few methods pasted here would be easiest for me as what I have is a combination of several different patches, so I doubt a simple diff would help much the other one I have incorporated is this http://groups.google.com/group/firewatir/browse_thread/thread/fe830c62c6034ac1 which refers to this site http://coderrr.wordpress.com/2007/10/15/patch-to-firewatir-and-jssh-to-support-testing-with-multiple-concurrent-firefox-browsers/ Paul On Wed, Apr 30, 2008 at 1:01 PM, Bret Pettichord wrote: > > > and Ive got > > a patch that makes the start up a bit better, but I cant remember why > > mine is different right now (possibly it better supports mac and win). > > Paul, could you please send us this patch. > > Bret > > > _______________________________________________ > Wtr-development mailing list > Wtr-development at rubyforge.org > http://rubyforge.org/mailman/listinfo/wtr-development > From aidy.lewis at googlemail.com Wed Apr 30 15:42:41 2008 From: aidy.lewis at googlemail.com (aidy lewis) Date: Wed, 30 Apr 2008 12:42:41 -0700 Subject: [Wtr-development] test - need not reply Message-ID: <7ac2300c0804301242u5b030262wfd0a5948b5d55b65@mail.gmail.com> From bret at pettichord.com Wed Apr 30 16:17:34 2008 From: bret at pettichord.com (Bret Pettichord) Date: Wed, 30 Apr 2008 15:17:34 -0500 Subject: [Wtr-development] Integrating Watir and FireWatir In-Reply-To: References: Message-ID: On Wed, Apr 30, 2008 at 2:18 PM, Paul Rogers wrote: > what format would you like? I guess the first few methods pasted here > would be easiest for me as what I have is a combination of several > different patches, so I doubt a simple diff would help much Actually a universal diff would be the most convenient form. Most IDE's can automatically create and apply patches in this form and it is therefore the most foolproof. If you have more than one, then send them all. Bret -- Bret Pettichord CTO, WatirCraft LLC Lead Developer, Watir, http://wtr.rubyforge.org Blog (Essays), http://www.io.com/~wazmo/blog MiniBlog (Links), http://feeds.feedburner.com/bretshotlist -------------- next part -------------- An HTML attachment was scrubbed... URL: From bret at pettichord.com Wed Apr 30 16:22:02 2008 From: bret at pettichord.com (Bret Pettichord) Date: Wed, 30 Apr 2008 15:22:02 -0500 Subject: [Wtr-development] Patch formats Message-ID: I just looked for a random email on the Ruby lists that I thought demonstrated well how to submit a patch. http://blade.nagaokaut.ac.jp/cgi-bin/scat.rb/ruby/ruby-core/11380 Bret -- Bret Pettichord CTO, WatirCraft LLC Lead Developer, Watir, http://wtr.rubyforge.org Blog (Essays), http://www.io.com/~wazmo/blog MiniBlog (Links), http://feeds.feedburner.com/bretshotlist -------------- next part -------------- An HTML attachment was scrubbed... URL: From bret at pettichord.com Tue Apr 29 20:27:29 2008 From: bret at pettichord.com (Bret Pettichord) Date: Tue, 29 Apr 2008 19:27:29 -0500 Subject: [Wtr-development] Integrating Watir and FireWatir Message-ID: Last November I wrote a report comparing Watir to FireWatir and laying out a plan forward for integrating the code bases. http://www.io.com/~wazmo/blog/archives/2007_11.html#000263 With one big exception, I still stand by this report and plan. In the report I expressed concern about FireWatir's dependency on JSSH, but I'm longer am worried about this. I've since learned that JSSH is in fact being maintained by the Mozilla project and that you can compile it and use it without problem with FireFox 3. In that report, I also blanched at the effort of getting the code bases in sync again. I still think it's a big effort, but with funding for Watir this now seems much less daunting. In fact, I think its the most important thing we need if we are going to grow the Watir community. In that report, I mostly focussed on the code bases themselves, but part of the challenge is also in pulling together the infrastructure for the projects. I recently spoke with Angrez Singh and we agreed to work out the details of a migration plan here. SVN. I want to have the Watir and FireWatir codebases in a single repository. Currently Watir is hosted at OpenQA.org and FireWatir is hosted at GoogleCode. Putting them into single repository is the only way that I know for allow us to safely remove duplications with a single commit. Part of the problem right now is simply that we have three slightly different versions of the FireWatir codebase itself: the official repo at googlecode, a copy with a few fixes to the testsuite in the vendor directory of the Watir codebase, and a private version that Paul Rogers has been applying patches to. So we need to get this sorted out too. Tests. As mentioned in the November report, I think we need to start by merging our test suites, so that we have a single suite that allows individual tests to be instrumented as applying to IE or Firefox or both. That way we won't have test duplication and can verify that the implementations have the same behavior. Gems. I just uploaded the FireWatir gem to the Rubyforge. Now you can just do a "gem install firewatir" without first downloading the gem from Google Code. Overall, our plan is to eventually migrate both projects to Watir.com, a new site that will host all Watir-related projects. I'd eventually like to see us pull together all the material from Google Code (FireWatir) and OpenQA (Watir). We'd also like to move the website from wtr.rubyforge.org, although Rubyforge may continue to be the best place to distribute gems from. Anyway, before I go into further details, I'm sure there are questions about this. Ask away! Bret -- Bret Pettichord CTO, WatirCraft LLC Lead Developer, Watir, http://wtr.rubyforge.org Blog (Essays), http://www.io.com/~wazmo/blog MiniBlog (Links), http://feeds.feedburner.com/bretshotlist -------------- next part -------------- An HTML attachment was scrubbed... URL: From paul.rogers at shaw.ca Tue Apr 29 23:07:48 2008 From: paul.rogers at shaw.ca (Paul Rogers) Date: Tue, 29 Apr 2008 21:07:48 -0600 Subject: [Wtr-development] Integrating Watir and FireWatir In-Reply-To: References: Message-ID: there are also some good patches flying around too. I cant remember where they are right now but they include - patch to get multiple browsers running, patch to speed up the start up process, and Ive got a patch that makes the start up a bit better, but I cant remember why mine is different right now (possibly it better supports mac and win). Paul On Tue, Apr 29, 2008 at 6:27 PM, Bret Pettichord wrote: > Last November I wrote a report comparing Watir to FireWatir and laying > out a plan forward for integrating the code bases. > > http://www.io.com/~wazmo/blog/archives/2007_11.html#000263 > > With one big exception, I still stand by this report and plan. In the > report I expressed concern about FireWatir's dependency on JSSH, but > I'm longer am worried about this. I've since learned that JSSH is in > fact being maintained by the Mozilla project and that you can compile > it and use it without problem with FireFox 3. > > In that report, I also blanched at the effort of getting the code > bases in sync again. I still think it's a big effort, but with funding > for Watir this now seems much less daunting. In fact, I think its the > most important thing we need if we are going to grow the Watir > community. > > In that report, I mostly focussed on the code bases themselves, but > part of the challenge is also in pulling together the infrastructure > for the projects. I recently spoke with Angrez Singh and we agreed to > work out the details of a migration plan here. > > SVN. I want to have the Watir and FireWatir codebases in a single > repository. Currently Watir is hosted at OpenQA.org and FireWatir is > hosted at GoogleCode. Putting them into single repository is the only > way that I know for allow us to safely remove duplications with a > single commit. Part of the problem right now is simply that we have > three slightly different versions of the FireWatir codebase itself: > the official repo at googlecode, a copy with a few fixes to the > testsuite in the vendor directory of the Watir codebase, and a private > version that Paul Rogers has been applying patches to. So we need to > get this sorted out too. > > Tests. As mentioned in the November report, I think we need to start > by merging our test suites, so that we have a single suite that allows > individual tests to be instrumented as applying to IE or Firefox or > both. That way we won't have test duplication and can verify that the > implementations have the same behavior. > > Gems. I just uploaded the FireWatir gem to the Rubyforge. Now you can > just do a "gem install firewatir" without first downloading the gem > from Google Code. > > Overall, our plan is to eventually migrate both projects to Watir.com, > a new site that will host all Watir-related projects. I'd eventually > like to see us pull together all the material from Google Code > (FireWatir) and OpenQA (Watir). We'd also like to move the website > from wtr.rubyforge.org, although Rubyforge may continue to be the best > place to distribute gems from. > > Anyway, before I go into further details, I'm sure there are questions > about this. Ask away! > > Bret > > -- > Bret Pettichord > CTO, WatirCraft LLC > Lead Developer, Watir, http://wtr.rubyforge.org > Blog (Essays), http://www.io.com/~wazmo/blog > MiniBlog (Links), http://feeds.feedburner.com/bretshotlist > _______________________________________________ > Wtr-development mailing list > Wtr-development at rubyforge.org > http://rubyforge.org/mailman/listinfo/wtr-development > From bret at pettichord.com Wed Apr 30 15:01:16 2008 From: bret at pettichord.com (Bret Pettichord) Date: Wed, 30 Apr 2008 14:01:16 -0500 Subject: [Wtr-development] Integrating Watir and FireWatir In-Reply-To: References: Message-ID: > > and Ive got > a patch that makes the start up a bit better, but I cant remember why > mine is different right now (possibly it better supports mac and win). Paul, could you please send us this patch. Bret -------------- next part -------------- An HTML attachment was scrubbed... URL: From bret at pettichord.com Wed Apr 30 15:02:49 2008 From: bret at pettichord.com (Bret Pettichord) Date: Wed, 30 Apr 2008 14:02:49 -0500 Subject: [Wtr-development] Integrating Watir and FireWatir In-Reply-To: References: Message-ID: Angrez, Amit, Could you all please comment on this plan before i go into further elaboration. I'm not even sure if you are reading this list. What do others think about this plan? Bret On Tue, Apr 29, 2008 at 7:27 PM, Bret Pettichord wrote: > Last November I wrote a report comparing Watir to FireWatir and laying > out a plan forward for integrating the code bases. > > http://www.io.com/~wazmo/blog/archives/2007_11.html#000263 > > With one big exception, I still stand by this report and plan. In the > report I expressed concern about FireWatir's dependency on JSSH, but > I'm longer am worried about this. I've since learned that JSSH is in > fact being maintained by the Mozilla project and that you can compile > it and use it without problem with FireFox 3. > > In that report, I also blanched at the effort of getting the code > bases in sync again. I still think it's a big effort, but with funding > for Watir this now seems much less daunting. In fact, I think its the > most important thing we need if we are going to grow the Watir > community. > > In that report, I mostly focussed on the code bases themselves, but > part of the challenge is also in pulling together the infrastructure > for the projects. I recently spoke with Angrez Singh and we agreed to > work out the details of a migration plan here. > > SVN. I want to have the Watir and FireWatir codebases in a single > repository. Currently Watir is hosted at OpenQA.org and FireWatir is > hosted at GoogleCode. Putting them into single repository is the only > way that I know for allow us to safely remove duplications with a > single commit. Part of the problem right now is simply that we have > three slightly different versions of the FireWatir codebase itself: > the official repo at googlecode, a copy with a few fixes to the > testsuite in the vendor directory of the Watir codebase, and a private > version that Paul Rogers has been applying patches to. So we need to > get this sorted out too. > > Tests. As mentioned in the November report, I think we need to start > by merging our test suites, so that we have a single suite that allows > individual tests to be instrumented as applying to IE or Firefox or > both. That way we won't have test duplication and can verify that the > implementations have the same behavior. > > Gems. I just uploaded the FireWatir gem to the Rubyforge. Now you can > just do a "gem install firewatir" without first downloading the gem > from Google Code. > > Overall, our plan is to eventually migrate both projects to Watir.com, > a new site that will host all Watir-related projects. I'd eventually > like to see us pull together all the material from Google Code > (FireWatir) and OpenQA (Watir). We'd also like to move the website > from wtr.rubyforge.org, although Rubyforge may continue to be the best > place to distribute gems from. > > Anyway, before I go into further details, I'm sure there are questions > about this. Ask away! > > Bret > > -- > Bret Pettichord > CTO, WatirCraft LLC > Lead Developer, Watir, http://wtr.rubyforge.org > Blog (Essays), http://www.io.com/~wazmo/blog > MiniBlog (Links), http://feeds.feedburner.com/bretshotlist -- Bret Pettichord CTO, WatirCraft LLC Lead Developer, Watir, http://wtr.rubyforge.org Blog (Essays), http://www.io.com/~wazmo/blog MiniBlog (Links), http://feeds.feedburner.com/bretshotlist -------------- next part -------------- An HTML attachment was scrubbed... URL: From paul.rogers at shaw.ca Wed Apr 30 15:18:23 2008 From: paul.rogers at shaw.ca (Paul Rogers) Date: Wed, 30 Apr 2008 13:18:23 -0600 Subject: [Wtr-development] Integrating Watir and FireWatir In-Reply-To: References: Message-ID: what format would you like? I guess the first few methods pasted here would be easiest for me as what I have is a combination of several different patches, so I doubt a simple diff would help much the other one I have incorporated is this http://groups.google.com/group/firewatir/browse_thread/thread/fe830c62c6034ac1 which refers to this site http://coderrr.wordpress.com/2007/10/15/patch-to-firewatir-and-jssh-to-support-testing-with-multiple-concurrent-firefox-browsers/ Paul On Wed, Apr 30, 2008 at 1:01 PM, Bret Pettichord wrote: > > > and Ive got > > a patch that makes the start up a bit better, but I cant remember why > > mine is different right now (possibly it better supports mac and win). > > Paul, could you please send us this patch. > > Bret > > > _______________________________________________ > Wtr-development mailing list > Wtr-development at rubyforge.org > http://rubyforge.org/mailman/listinfo/wtr-development > From aidy.lewis at googlemail.com Wed Apr 30 15:42:41 2008 From: aidy.lewis at googlemail.com (aidy lewis) Date: Wed, 30 Apr 2008 12:42:41 -0700 Subject: [Wtr-development] test - need not reply Message-ID: <7ac2300c0804301242u5b030262wfd0a5948b5d55b65@mail.gmail.com> From bret at pettichord.com Wed Apr 30 16:17:34 2008 From: bret at pettichord.com (Bret Pettichord) Date: Wed, 30 Apr 2008 15:17:34 -0500 Subject: [Wtr-development] Integrating Watir and FireWatir In-Reply-To: References: Message-ID: On Wed, Apr 30, 2008 at 2:18 PM, Paul Rogers wrote: > what format would you like? I guess the first few methods pasted here > would be easiest for me as what I have is a combination of several > different patches, so I doubt a simple diff would help much Actually a universal diff would be the most convenient form. Most IDE's can automatically create and apply patches in this form and it is therefore the most foolproof. If you have more than one, then send them all. Bret -- Bret Pettichord CTO, WatirCraft LLC Lead Developer, Watir, http://wtr.rubyforge.org Blog (Essays), http://www.io.com/~wazmo/blog MiniBlog (Links), http://feeds.feedburner.com/bretshotlist -------------- next part -------------- An HTML attachment was scrubbed... URL: From bret at pettichord.com Wed Apr 30 16:22:02 2008 From: bret at pettichord.com (Bret Pettichord) Date: Wed, 30 Apr 2008 15:22:02 -0500 Subject: [Wtr-development] Patch formats Message-ID: I just looked for a random email on the Ruby lists that I thought demonstrated well how to submit a patch. http://blade.nagaokaut.ac.jp/cgi-bin/scat.rb/ruby/ruby-core/11380 Bret -- Bret Pettichord CTO, WatirCraft LLC Lead Developer, Watir, http://wtr.rubyforge.org Blog (Essays), http://www.io.com/~wazmo/blog MiniBlog (Links), http://feeds.feedburner.com/bretshotlist -------------- next part -------------- An HTML attachment was scrubbed... URL: From bret at pettichord.com Tue Apr 29 20:27:29 2008 From: bret at pettichord.com (Bret Pettichord) Date: Tue, 29 Apr 2008 19:27:29 -0500 Subject: [Wtr-development] Integrating Watir and FireWatir Message-ID: Last November I wrote a report comparing Watir to FireWatir and laying out a plan forward for integrating the code bases. http://www.io.com/~wazmo/blog/archives/2007_11.html#000263 With one big exception, I still stand by this report and plan. In the report I expressed concern about FireWatir's dependency on JSSH, but I'm longer am worried about this. I've since learned that JSSH is in fact being maintained by the Mozilla project and that you can compile it and use it without problem with FireFox 3. In that report, I also blanched at the effort of getting the code bases in sync again. I still think it's a big effort, but with funding for Watir this now seems much less daunting. In fact, I think its the most important thing we need if we are going to grow the Watir community. In that report, I mostly focussed on the code bases themselves, but part of the challenge is also in pulling together the infrastructure for the projects. I recently spoke with Angrez Singh and we agreed to work out the details of a migration plan here. SVN. I want to have the Watir and FireWatir codebases in a single repository. Currently Watir is hosted at OpenQA.org and FireWatir is hosted at GoogleCode. Putting them into single repository is the only way that I know for allow us to safely remove duplications with a single commit. Part of the problem right now is simply that we have three slightly different versions of the FireWatir codebase itself: the official repo at googlecode, a copy with a few fixes to the testsuite in the vendor directory of the Watir codebase, and a private version that Paul Rogers has been applying patches to. So we need to get this sorted out too. Tests. As mentioned in the November report, I think we need to start by merging our test suites, so that we have a single suite that allows individual tests to be instrumented as applying to IE or Firefox or both. That way we won't have test duplication and can verify that the implementations have the same behavior. Gems. I just uploaded the FireWatir gem to the Rubyforge. Now you can just do a "gem install firewatir" without first downloading the gem from Google Code. Overall, our plan is to eventually migrate both projects to Watir.com, a new site that will host all Watir-related projects. I'd eventually like to see us pull together all the material from Google Code (FireWatir) and OpenQA (Watir). We'd also like to move the website from wtr.rubyforge.org, although Rubyforge may continue to be the best place to distribute gems from. Anyway, before I go into further details, I'm sure there are questions about this. Ask away! Bret -- Bret Pettichord CTO, WatirCraft LLC Lead Developer, Watir, http://wtr.rubyforge.org Blog (Essays), http://www.io.com/~wazmo/blog MiniBlog (Links), http://feeds.feedburner.com/bretshotlist -------------- next part -------------- An HTML attachment was scrubbed... URL: From paul.rogers at shaw.ca Tue Apr 29 23:07:48 2008 From: paul.rogers at shaw.ca (Paul Rogers) Date: Tue, 29 Apr 2008 21:07:48 -0600 Subject: [Wtr-development] Integrating Watir and FireWatir In-Reply-To: References: Message-ID: there are also some good patches flying around too. I cant remember where they are right now but they include - patch to get multiple browsers running, patch to speed up the start up process, and Ive got a patch that makes the start up a bit better, but I cant remember why mine is different right now (possibly it better supports mac and win). Paul On Tue, Apr 29, 2008 at 6:27 PM, Bret Pettichord wrote: > Last November I wrote a report comparing Watir to FireWatir and laying > out a plan forward for integrating the code bases. > > http://www.io.com/~wazmo/blog/archives/2007_11.html#000263 > > With one big exception, I still stand by this report and plan. In the > report I expressed concern about FireWatir's dependency on JSSH, but > I'm longer am worried about this. I've since learned that JSSH is in > fact being maintained by the Mozilla project and that you can compile > it and use it without problem with FireFox 3. > > In that report, I also blanched at the effort of getting the code > bases in sync again. I still think it's a big effort, but with funding > for Watir this now seems much less daunting. In fact, I think its the > most important thing we need if we are going to grow the Watir > community. > > In that report, I mostly focussed on the code bases themselves, but > part of the challenge is also in pulling together the infrastructure > for the projects. I recently spoke with Angrez Singh and we agreed to > work out the details of a migration plan here. > > SVN. I want to have the Watir and FireWatir codebases in a single > repository. Currently Watir is hosted at OpenQA.org and FireWatir is > hosted at GoogleCode. Putting them into single repository is the only > way that I know for allow us to safely remove duplications with a > single commit. Part of the problem right now is simply that we have > three slightly different versions of the FireWatir codebase itself: > the official repo at googlecode, a copy with a few fixes to the > testsuite in the vendor directory of the Watir codebase, and a private > version that Paul Rogers has been applying patches to. So we need to > get this sorted out too. > > Tests. As mentioned in the November report, I think we need to start > by merging our test suites, so that we have a single suite that allows > individual tests to be instrumented as applying to IE or Firefox or > both. That way we won't have test duplication and can verify that the > implementations have the same behavior. > > Gems. I just uploaded the FireWatir gem to the Rubyforge. Now you can > just do a "gem install firewatir" without first downloading the gem > from Google Code. > > Overall, our plan is to eventually migrate both projects to Watir.com, > a new site that will host all Watir-related projects. I'd eventually > like to see us pull together all the material from Google Code > (FireWatir) and OpenQA (Watir). We'd also like to move the website > from wtr.rubyforge.org, although Rubyforge may continue to be the best > place to distribute gems from. > > Anyway, before I go into further details, I'm sure there are questions > about this. Ask away! > > Bret > > -- > Bret Pettichord > CTO, WatirCraft LLC > Lead Developer, Watir, http://wtr.rubyforge.org > Blog (Essays), http://www.io.com/~wazmo/blog > MiniBlog (Links), http://feeds.feedburner.com/bretshotlist > _______________________________________________ > Wtr-development mailing list > Wtr-development at rubyforge.org > http://rubyforge.org/mailman/listinfo/wtr-development > From bret at pettichord.com Wed Apr 30 15:01:16 2008 From: bret at pettichord.com (Bret Pettichord) Date: Wed, 30 Apr 2008 14:01:16 -0500 Subject: [Wtr-development] Integrating Watir and FireWatir In-Reply-To: References: Message-ID: > > and Ive got > a patch that makes the start up a bit better, but I cant remember why > mine is different right now (possibly it better supports mac and win). Paul, could you please send us this patch. Bret -------------- next part -------------- An HTML attachment was scrubbed... URL: From bret at pettichord.com Wed Apr 30 15:02:49 2008 From: bret at pettichord.com (Bret Pettichord) Date: Wed, 30 Apr 2008 14:02:49 -0500 Subject: [Wtr-development] Integrating Watir and FireWatir In-Reply-To: References: Message-ID: Angrez, Amit, Could you all please comment on this plan before i go into further elaboration. I'm not even sure if you are reading this list. What do others think about this plan? Bret On Tue, Apr 29, 2008 at 7:27 PM, Bret Pettichord wrote: > Last November I wrote a report comparing Watir to FireWatir and laying > out a plan forward for integrating the code bases. > > http://www.io.com/~wazmo/blog/archives/2007_11.html#000263 > > With one big exception, I still stand by this report and plan. In the > report I expressed concern about FireWatir's dependency on JSSH, but > I'm longer am worried about this. I've since learned that JSSH is in > fact being maintained by the Mozilla project and that you can compile > it and use it without problem with FireFox 3. > > In that report, I also blanched at the effort of getting the code > bases in sync again. I still think it's a big effort, but with funding > for Watir this now seems much less daunting. In fact, I think its the > most important thing we need if we are going to grow the Watir > community. > > In that report, I mostly focussed on the code bases themselves, but > part of the challenge is also in pulling together the infrastructure > for the projects. I recently spoke with Angrez Singh and we agreed to > work out the details of a migration plan here. > > SVN. I want to have the Watir and FireWatir codebases in a single > repository. Currently Watir is hosted at OpenQA.org and FireWatir is > hosted at GoogleCode. Putting them into single repository is the only > way that I know for allow us to safely remove duplications with a > single commit. Part of the problem right now is simply that we have > three slightly different versions of the FireWatir codebase itself: > the official repo at googlecode, a copy with a few fixes to the > testsuite in the vendor directory of the Watir codebase, and a private > version that Paul Rogers has been applying patches to. So we need to > get this sorted out too. > > Tests. As mentioned in the November report, I think we need to start > by merging our test suites, so that we have a single suite that allows > individual tests to be instrumented as applying to IE or Firefox or > both. That way we won't have test duplication and can verify that the > implementations have the same behavior. > > Gems. I just uploaded the FireWatir gem to the Rubyforge. Now you can > just do a "gem install firewatir" without first downloading the gem > from Google Code. > > Overall, our plan is to eventually migrate both projects to Watir.com, > a new site that will host all Watir-related projects. I'd eventually > like to see us pull together all the material from Google Code > (FireWatir) and OpenQA (Watir). We'd also like to move the website > from wtr.rubyforge.org, although Rubyforge may continue to be the best > place to distribute gems from. > > Anyway, before I go into further details, I'm sure there are questions > about this. Ask away! > > Bret > > -- > Bret Pettichord > CTO, WatirCraft LLC > Lead Developer, Watir, http://wtr.rubyforge.org > Blog (Essays), http://www.io.com/~wazmo/blog > MiniBlog (Links), http://feeds.feedburner.com/bretshotlist -- Bret Pettichord CTO, WatirCraft LLC Lead Developer, Watir, http://wtr.rubyforge.org Blog (Essays), http://www.io.com/~wazmo/blog MiniBlog (Links), http://feeds.feedburner.com/bretshotlist -------------- next part -------------- An HTML attachment was scrubbed... URL: From paul.rogers at shaw.ca Wed Apr 30 15:18:23 2008 From: paul.rogers at shaw.ca (Paul Rogers) Date: Wed, 30 Apr 2008 13:18:23 -0600 Subject: [Wtr-development] Integrating Watir and FireWatir In-Reply-To: References: Message-ID: what format would you like? I guess the first few methods pasted here would be easiest for me as what I have is a combination of several different patches, so I doubt a simple diff would help much the other one I have incorporated is this http://groups.google.com/group/firewatir/browse_thread/thread/fe830c62c6034ac1 which refers to this site http://coderrr.wordpress.com/2007/10/15/patch-to-firewatir-and-jssh-to-support-testing-with-multiple-concurrent-firefox-browsers/ Paul On Wed, Apr 30, 2008 at 1:01 PM, Bret Pettichord wrote: > > > and Ive got > > a patch that makes the start up a bit better, but I cant remember why > > mine is different right now (possibly it better supports mac and win). > > Paul, could you please send us this patch. > > Bret > > > _______________________________________________ > Wtr-development mailing list > Wtr-development at rubyforge.org > http://rubyforge.org/mailman/listinfo/wtr-development > From aidy.lewis at googlemail.com Wed Apr 30 15:42:41 2008 From: aidy.lewis at googlemail.com (aidy lewis) Date: Wed, 30 Apr 2008 12:42:41 -0700 Subject: [Wtr-development] test - need not reply Message-ID: <7ac2300c0804301242u5b030262wfd0a5948b5d55b65@mail.gmail.com> From bret at pettichord.com Wed Apr 30 16:17:34 2008 From: bret at pettichord.com (Bret Pettichord) Date: Wed, 30 Apr 2008 15:17:34 -0500 Subject: [Wtr-development] Integrating Watir and FireWatir In-Reply-To: References: Message-ID: On Wed, Apr 30, 2008 at 2:18 PM, Paul Rogers wrote: > what format would you like? I guess the first few methods pasted here > would be easiest for me as what I have is a combination of several > different patches, so I doubt a simple diff would help much Actually a universal diff would be the most convenient form. Most IDE's can automatically create and apply patches in this form and it is therefore the most foolproof. If you have more than one, then send them all. Bret -- Bret Pettichord CTO, WatirCraft LLC Lead Developer, Watir, http://wtr.rubyforge.org Blog (Essays), http://www.io.com/~wazmo/blog MiniBlog (Links), http://feeds.feedburner.com/bretshotlist -------------- next part -------------- An HTML attachment was scrubbed... URL: From bret at pettichord.com Wed Apr 30 16:22:02 2008 From: bret at pettichord.com (Bret Pettichord) Date: Wed, 30 Apr 2008 15:22:02 -0500 Subject: [Wtr-development] Patch formats Message-ID: I just looked for a random email on the Ruby lists that I thought demonstrated well how to submit a patch. http://blade.nagaokaut.ac.jp/cgi-bin/scat.rb/ruby/ruby-core/11380 Bret -- Bret Pettichord CTO, WatirCraft LLC Lead Developer, Watir, http://wtr.rubyforge.org Blog (Essays), http://www.io.com/~wazmo/blog MiniBlog (Links), http://feeds.feedburner.com/bretshotlist -------------- next part -------------- An HTML attachment was scrubbed... URL: