Cool, sounds we are on the page now.
In the flow I mentioned, the search criteria can actually be extended
to the Locator Query Language (LQL) I talked before. Here "Language"
may not be the right term and seems scaring somehow, what we need is
not only search keywords, but also a set of operators to support the
search just like SQL.
Still take the button example and assume we have a list of buttons,
for some methods, we need to get all statuses for the buttons, where
the query is like "return all buttons under tag X". And for some
methods, we need to act on a single button, where we should use the
query "return the button under tag X where its ID is Y". In this way,
the LQL will be used internally (i.e., inside Tellurium core and
Tellurium Engine) to make it easier to for us to write query in the
Tellurium object and generate the correct JQuery in the Engine.
As a result, the flow really looks like,
UI jlocator definition
| attributes
UI object
| LQL
EventHandler or Data Accessor
|
Tellurium Connector
|
Tellurium Engine
| LQL interpreter
| JQuery
UI
But what syntax and operators we should design for LQL really depends
on JQuery capabilities if we rely on JQuery only. I don't have time to
think deeply about it yet. You are welcome to think of this if you
have some free time.
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
-~----------~----~----~----~------~----~------~--~---
