At 12:19 AM 8/10/2005, Scott Hanselman wrote:
Ya, I really don't like the name either, as it (deeply) exposes the
implementation, IMHO. That said, here's my hypocritical votes:
* spawn_eval
* forked_eval
* eval_newthread
* newthread_eval
* run_on_new_thread
of these, i liked forked_eval the best...
That said, why not just lie to us (as object models are wont to do) and have
the API match my intent:
ie.alert.dismiss_when_shown(:value, "OK")
ie.button(:name,"btnfoo").click
This is an interesting idea. It does require the inverted sequencing that i
was trying to avoid, but the result is, overall, probably easier to understand.
Is "ie.alert" more intuitive than "ie.dialog"? What about "ie.popup"? One
principle that i've tried to following in naming Watir methods is to use
the HTML or JavaScript names for things. The JavaScript name is in fact
"alert" (and "confirm").
Bret
_____________________
Bret Pettichord
www.pettichord.com
_______________________________________________
Wtr-general mailing list
[email protected]
http://rubyforge.org/mailman/listinfo/wtr-general
