These days, my policy on adding new methods to watir is "Start with No" http://gettingreal.37signals.com/ch05_Start_With_No.php
But there are some methods that I would like to see us add. I've previously mentioned my reluctance even then to add them for only one browser. A feature that fits this category is adding browser.element and browser.elements. http://jira.openqa.org/browse/WTR-103 Hugh McGowan wrote the code for this in his github fork and I've pulled it into a separate branch. http://github.com/bret/watir/tree/element-method Before pulling this into trunk, i would like to see these methods added to firewatir as well. By making a separate branch, I'm hoping to encourage some one to do this work. I also have plans to create feature branches for the following: * Change to zero-based indexing * Changing wait parameters to those recently recommended by Tim * Adding display_value methods from watircraft * Add a new match (===) operator for watir elements (based on display_value) * Reworking table classes * Reworking radio class * Using jeweller to create gems (removing hoe). I also encourage others who would like to work on these or other features to work on topic branches. (This is all in the context of things that we'd add after the 1.6.5 release.) Bret -- Bret Pettichord Lead Developer, Watir, www.watir.com Blog, www.io.com/~wazmo/blog Twitter, www.twitter.com/bpettichord
_______________________________________________ Wtr-development mailing list [email protected] http://rubyforge.org/mailman/listinfo/wtr-development
