Can't resist adding this gratuitous and unsolicited advice: If an application can only have one status at a time, resist any urge you might feel to store status in a series of boolean fields in applications. Instead, have your controller just store the id of the selected status in application.status_id.
That way you don't have to worry that an application might wind up with >1 of those booleans checked at a time, you should be able to add/rename statuses at will, etc. -----Original Message----- From: [email protected] [mailto:[email protected]] On Behalf Of Ar Chron Sent: Tuesday, January 13, 2009 9:01 AM To: [email protected] Subject: [Rails] Re: radio buttons and whatnot In your case, have the appropriate controller read in the statuses info and hand that to the view... @statuses = Status.find(:all, :order => 'something') Then the view (or a partial) can do something like: @statuses.each do |this_status| radio_button("application", "status", this_status.value) end or sumfink like that... -- Posted via http://www.ruby-forum.com/. --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
