@Patrick Doyle I don't know about the first suggestion, but I know that the second option can work but brings up some problems... For example, when the page is refreshed the user looses all of the new fields. Also, it gets hard to manage in Javascript (at least the way that is below) because it gets a lot of code.
@Michael Hendrickx Yeah, I kind of assumed it was hard to hard to understand. :) I have wrote a quick example using Javascript, which is below this text. I know how to do this in Javascript, but there are some problems so I am looking if there is a way to do this in Ruby on Rails. The problems with doing it in Javascript are outlined above. @Dejan Dimic As I said, I kind of guessed that it would be hard to understand. I hope the code below makes more sense, but if not just say so and I will try to explain it better. Pretty much, a button/link creates a new object and shows it on the page. Preferably it would not loose the new fields (and their values) on a refresh. I am doing a rewrite of a web application in Ruby on Rails, and am wondering how to avoid doing this in Javascript again. I suppose there really isn't a reason why I need to do this in Ruby on Rails, but Javascript brings up some problems and I think it may be easier in Ruby on Rails in general. If anyone could give me some advice about this, it would be great. --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
