John, The first step, which i really do need your help with in all this is getting the custom user extensions support working in tellurium. We need to modify the tellurium config file to allow for both: using a predefined user-extensions.js or overriding it with your own. we will need a tellurium user extensions js file where i will dump all my jquery selector logic. I think we need consensus on where the tellurium-user-extensions.js will live.
At my job, i am nearing that time when i need to write a bunch of functional tests again, and it would be a good time to start doing more work on the jquery selector. On Mar 19, 9:44 am, John <[email protected]> wrote: > Good point. If we can use JQuery directly, we do not have to waste > time to convert to CSS selector. But we need to get this into > Tellurium > core 0.6.0, at least some part of it. > > On Mar 19, 9:06 am, Mikhail Koryak <[email protected]> wrote: > > > I wanted to chime in here: > > > css selectors would be easier to implement then jquery selectors, on > > the other hand, id rather implement jquery selectors because we will > > get the following extra features: > > > CSS 3 selectors (unless that is what css selectors support) > > better user script support (this is 99% done already) > > the ability to get data from multiple elements in one call > > > John, i know you wanted to build LQL which would be translated into > > jquery selectors in either the user extension javascript, or in the > > lowest level of tellurium core. I want to start looking at this again > > in the near future. I think we need to get this ball rolling again --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
