Hi Richard, Glad that helped. On the IDs, it sounds like that means you won't have duplicated IDs on the page, which was my only concern. It also sounds like they're sufficiently complex (rather than just being 1..n) that sticking with this DOM-based solution is probably best (allowing for my ignorance of the overall context) rather than rewriting it to work from IDs instead.
Happy coding, -- T.J. Crowder tj / crowder software / com Independent Software Engineer, consulting services available On Jan 14, 2:51 pm, RNHurt <[email protected]> wrote: > Again, brilliant help on everything guys! > > I worked on this thing for quite a while last night and eventually got > it to work in a round-about sort-of way. I used something like > cell.getFirstChild().getSibling().value; a really ugly hack. I ended > up making the changes as suggested by T.J. and it works beautifully. > > About the IDs of each field; since I'm running RoR and I want to > update the database with the latest data everytime someone changes a > score, all of the IDs will be set to something like a hash of student > id and assignment id. That way when it gets sent to my controller I > can split it back out again and use the info to update my model. Does > this sound correct? Or is there a neat, better way to do this? > > Thanx! > Richard --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Prototype & script.aculo.us" 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/prototype-scriptaculous?hl=en -~----------~----~----~----~------~----~------~--~---
