Mikhail,
I looked at your example for using JQuery to creating jqlocator in
Tellurium, which is great for people who understand the JQuery very
well. I like it. However, there is another usage for JQuery with
Tellurium. The main idea is to use JQuery selectors to replace XPaths
under the hood, i.e., in Selenium core, and keep the Tellurium
DslContext the same or add new methods to it. That is to say, we can
still use clocator (or jlocator with enhanced capability with JQuery,
which will be just a hash of attributes without any javascript) in
Tellurium and modify Selenium core using JQuery:
jlocator (hash of attributes)
|
Modified Selenium RC
|
New Selenium core with JQuery (or
Tellurium Engine prototype)
In this way, we have the following advantages
1) People who do not understand JQuery can also take advantage of its
capability
2) JQuery selectors may be faster for some Web browsers such as IE
than XPaths
3) Remove redundant javascript code from Tellurium so that people do
not need to deal with Javascript directly (make javascript
encapsulated like the Ruby on Rails framework)
4) Add more functionalities to Selenium Core with the support of
JQuery
What do you think?
Thanks,
Jian
--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups
"tellurium-users" group.
To post to this group, send email to [email protected]
To unsubscribe from this group, send email to [EMAIL PROTECTED]
For more options, visit this group at
http://groups.google.com/group/tellurium-users?hl=en
-~----------~----~----~----~------~----~------~--~---
