> My focus is to glue the ruby-based watir-webdriver and selenium-> webdriver> code together with existing (or new if we have to) safari driver code

watir-webdriver doesn't need any code changes to work with new driversintroduced in the selenium-webdriver back-end. As long as the Safaridriver honors the semantics of the WebDriver API, it should all justwork from the Watir side.

There's no gemspec file, but you can build the gem using `rake gem:gem` inyour working copy.

> After we get the ruby glue code in place, then we can see what safari-specific> code is best to use (your java version, safariwatir version,etc).

Since the Safari driver is based on the remote driver, the amount of work needed to make itwork from Ruby is practically negligible. Ifyou're interested in how the Safari driver isimplemented natively,you should look at the branch linked in Miklos email.

EVEN MORE RESPONSES (Jari's Emails: 3/3/2010)

Which gem are you talking about watir-webdriver or selenium-webdriver? selenium-webdriver