Hi Jian, In this case all of the tbody elements have identical structures, so each table shouldn't be much more complicated to define.
Whether this would be the case for everyone I couldn't guess, so if implemented there should probably be a mechanism for overriding tbody definitions in the same way as rows and columns can be overriden now. Thanks again for your support and all your work on Tellurium. On Feb 27, 3:22 pm, John <[email protected]> wrote: > Hi Dominicm, > > Certainly, you have very good point for adding multiple tbody elements > inside the table. > My concern is not to make the UI template definition too complicated. > As you said, you > may have dynamic number of tbody elements, will they have the same > structure or different > structures? > > I will consider your suggestion. > > Thanks, > > Jian > > On Feb 27, 6:33 am, dominicm <[email protected]> wrote: > > > > > Hi John, > > > I've tried using the new table functionality but it will not work with > > our code as the number of tbody elements is dynamic. Tables like this > > appear all over our site. > > > Looking at the HTML spec for tables, it says: > > "Table rows may be grouped into a table head, table foot, and one or > > more table body sections". > > > This suggests that the use of multiple tbody elements is standard. > > > Would it not be better to be able to access the table as > > > table[tbody][row][column] > > > With a new keyword of something like multipleBody:'true' > > > This value would default to false and present table[row][column] in > > the same way it does already.- Hide quoted text - > > - Show quoted text - --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
