On Wed, Jan 27, 2010 at 11:02 AM, Jari Bakken <[email protected]> wrote:
> On Wed, Jan 27, 2010 at 6:03 PM, Ethan <[email protected]> wrote: > > No on the pull request - at the moment, there is too much that isn't > > entirely resolved about things that have changed in my fork. There is > also > > just a lot changed - sufficient quantity that it warrants discussion here > I > > think. I'd like to get things resolved in order to get my changes back > in, > > hopefully. But, that does not seem to be happening given the lack of much > of > > any response. > > For my part, interest in the 1.X code base has sharply declined after > I started work on WebDriver, as I'm sure you can understand. > > I think also timing wise, this has been a bit of a challenge. With the holidays, time off, finally my first 2 weeks off in about 9 years; short time back and then out for another conference, and during that time work has piled up. That's my own situation, but I definitely notice a slow down in open source projects at the end of the year. Honestly there are ton of changes in your work which also makes it hard to tackle all at once. If there is a way to slightly break it down into manageable chunks, we can probably take those on one at a time. Hopefully that's possible so we can digest this in slow bites. :) Let me know if that sounds reasonable. > > My work, I think, greatly improves implementation as far as it goes > relying > > on JSSH and WIN32OLE. This may not end up being so useful if webdriver is > > the direction watir is headed. I think that has significant shortcomings, > > but that's another discussion. > > I'd be very interested to hear what you think are significant > shortcomings of the WebDriver approach. > The 1.x.x version will still continue for quite a while, as the switch to 2.x introduces some large changes that some people might not want to take on with their existing test suites. I, for one, may have to use 1.x for some time given the amount of tests that we currently have, the number of QA Engineers working on our existing codebase and the cost to switch. I'm also curious about your thoughts on the Webdriver approach, since I pushed this general direction several months ago, think it has great merit for a long term solution and Jari has done some amazing work getting the Ruby bindings up, tested and really to a quick alpha or whatever you want to call it, very early. Btw, I don't say it often enough but wow Jari. :) > _______________________________________________ > Wtr-development mailing list > [email protected] > http://rubyforge.org/mailman/listinfo/wtr-development >
_______________________________________________ Wtr-development mailing list [email protected] http://rubyforge.org/mailman/listinfo/wtr-development
