Dave, First of all, you can look at the CVS code, but it would be better to look at our code on SVN (at openqa.org) or even just look at the versions that i posted to wiki.openqa.org the other day. They are both more current.
The support for windows popups, however, is not really ready for testing yet. (The support for modal web popups, however, is 98% complete.) All the core-tests work, so the core code is stable. I've frequently pointed people to this build when they have found bugs in 1.4.1 that are fixed in dev and they usually come back satisfied. We've just started final regression testing on our main product at work, for the first release in six months, so that is probably going to be taking most of my energy for the next few weeks. I am in the process of moving the roadmap to jira, so we have an online map of what needs to be done to complete the release. Since moving the code to OpenQA, there are a lot of loose ends to tie up to explain what is going on. If you see one, it would help a lot if you could tie it off for us. The more help i get with the FAQ and the website, etc, the more time i have to write ruby code. Bret On 3/21/06, Dave Burt <[EMAIL PROTECTED]> wrote: > Hi Bret and anybody else hacking on the Watir library, > > What's the status on Watir 1.5? > > The changes I've heard about include effective ways of handling popups > (confirm, alert, modal web dialogs, save-as) and more consistent > returning of Watir wrappers rather than straight WIN32OLE handles, and > I'm looking forward to the future. > > Do you have a time-frame in mind for a release? > > If I go to RubyForge and download stuff from CVS, should I expect > problems with any particular areas? > > Thanks, > Dave > > _______________________________________________ > Wtr-general mailing list > [email protected] > http://rubyforge.org/mailman/listinfo/wtr-general > _______________________________________________ Wtr-general mailing list [email protected] http://rubyforge.org/mailman/listinfo/wtr-general
