thats a pretty idea, but how close is each browser to the spec? ( or maybe this is a different level to the where the browsers are so it doesnt matter I didnt read much of the other stuff so not sure.)
Paul On Fri, Oct 30, 2009 at 12:13 PM, Jari Bakken <[email protected]> wrote: > As the WebDriver bindings are maturing (the initial commit to the > WebDriver tree will happen very soon), I would like to do a spike on > the Watir code built on WebDriver as the next step. I'm thinking I > will do a new repo on GitHub named "watir2-spike" or similar. > > While thinking about how to structure the code, I wrote this example > which is pretty close to the API that was discussed in another thread > with Ethan. So for element definitions: > > http://gist.github.com/222592 > > While looking at that I realized it's pretty declarative, which gave > me the idea that this code (or some representation of that data) could > possibly be generated from the XHTML or HTML5 specifications. So with > a small core of metaprogramming that builds all the Watir element > classes based on some declarative definition, the actual Watir code > base would become pretty small and easy to maintain. I'm not sure if > it's really feasible, but I'd like to give this a try for my spike. > > WDYT? > _______________________________________________ > 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
