I have a scheme that doesn't require this code to be in separate ruby files
at all. I've tested it out and it works.
Right now, using this code looks like this:
ie.remote_eval <<-END
button(:name, 'foo').click
END
dialog.button('Yes').click
I'd appreciate comments on this interface, and the names it uses
(remote_eval, dialog).
Note that the first button click is run in a separate process (that
blocks). This allows the script actions to appear in a logical sequence,
rather than the inverted one that you need when the dialog button click is
in the remote process.
Bret
At 01:31 PM 7/27/2005, Paul Rogers wrote:
The scripts that handle pop ups are in the unit test directory
jscriptExtraAlert.rb
jscriptExtraConfirmCancel.rb
jscriptExtraConfirmOk.rb
jscriptPushButton.rb
I suggest we move these to a better location -
The C:\ruby\lib\ruby\site_ruby\1.8\watir seems like the best place ( or
maybe another dir below)
We can then maybe add some methods to launch these from watir directly -
ie.launch_js_confirm_clicker()
Or similar. I think this would be one small step to making these popups
easier to deal with.
Any suggestions?
Paul
_______________________________________________
Wtr-general mailing list
[email protected]
http://rubyforge.org/mailman/listinfo/wtr-general
_____________________
Bret Pettichord
www.pettichord.com
_______________________________________________
Wtr-general mailing list
[email protected]
http://rubyforge.org/mailman/listinfo/wtr-general
