Just wanted to let you know that i am not dead, we are nearing an end of a big release, we all know how that goes.
anyway, i have been giving this more though. I was at first somewhat opposed to the idea of LQL, but now i think it will be necessary for the following reasons: i can pass jquery to selenium, but only selectors, and functions, this is because the selector is a string, and a function can be encoded as a string, and then i call eval() in javascript on it to 'decode' the function again. passing jquery selectors is nice but sometimes not sufficient to select what i want, with a function i can select anything i want, but writing a function in java is not very easy, especially if you get a syntax error. with LQL, we can build something like a CFL which can be encoded in as a list of strings, to be passed to javascript, and parsed into selectors, function calls and everything in between, without having to worry about having syntax errors. anyway, ill be thinking about this more, and hopefully even implementing after things settle down around here On Dec 11, 6:10 pm, [email protected] wrote: > 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 -~----------~----~----~----~------~----~------~--~---
