That makes sense for the table object, because you can supply the
table id, and from that id you can locate the table, and from that can
get the table html and find out exactly how many rows, columns, and
headers it has, and the generate the xpath to access any cell. so just
by knowing the id of the table, you can have methods to access cells,
you can have a method to get the text of all elements in a row or a
column etc.
But what i am having a problem with is the following scenario: lets
say you have a jlocator that looks like this:
ui.Button(uid:"button", jlocator:"button")
the jquery $("button") is what was asked for, which selects all DOM
elements that have the tag button. Now we have a collection of buttons
selected in the uid button. what happens when you write
click "button"
should i click the 1st element in the collection of buttons? is this
what the user expects to happen?
on the other hand, maybe we should constrain existing elements such as
ui.Button to expect the jquery to select a single element, and add new
objects such as ui.ButtonCollection to support multiple elements. in
this example ButtonCollection would have methods that work well
collections, such as getting multiple elements, etc.
Back to your original question:
i can add suppport for generating different jquery for each object
under the hood, but i will need help defining what that jquery should
be
On Dec 10, 10:42 am, [EMAIL PROTECTED] wrote:
> Sorry, I did not reply to the list for last post.
>
> For methods that return void, a single element, or multiple elements,
> the passed in search criteria should be different and that part should
> be handled at the Tellurium core level, i.e., inside the Tellurium
> object. For example, you can take a look at how a cell, a row, or a
> column are handled in the Table object. For jlocator case, we need to
> do this in a similar way, i.e., pass different search criteria.
>
> Thanks,
>
> Jian
>
> Jian,
> that sounds good, i think that all Action methods, the ones that
> return void, should act on a single element, that makes the most
> sense, and should throw an error multiple elements are passed in. on
> the other hand the accessor methods should allow for multiple elements
> to be passed in.
>
> does this sound right to you?
--~--~---------~--~----~------------~-------~--~----~
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
-~----------~----~----~----~------~----~------~--~---
