Hi Mikel. Thanks for that... the HTML5 way looks good, though for the initial version may just go the class route :-)
Thanks Peter On Mar 3, 12:22 pm, Mikel Lindsaar <[email protected]> wrote: > On Wed, Mar 3, 2010 at 7:20 AM, ptorrsmith <[email protected]> wrote: > > Any suggestions as to how to structure the form so each intersect > > field is aware of its person_id and it's want_id and this is passed > > back on the XHR for updating? > > Add something to each cell as you generate it which corresponds to the > column and row the cell is in. > > If you want to do it the html5 way, you can add data-attributes as you > generate the table - which semantically would be the best bet. > > If you don't want to go that way, add a class to each cell, one for > each column (you work out the row by just looking at the class of the > nearest parent tr), then get your cell to work out what classes it has > as they are updated. > > Mikel > > --http://lindsaar.net/ -- You received this message because you are subscribed to the Google Groups "Ruby on Rails: Talk" 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/rubyonrails-talk?hl=en.
