I've done this before in general, create an attribute (call it :stage) - base your view names and validation rules upon :stage
:stage can be virtual, or if you store it you could allow someone to return to entry later for a more advanced implementation you could use a state machine (instead of stage) - which may give you more power if you want to process the data entered asynchronously On Sat, Feb 9, 2013 at 10:24 AM, Phil Bee <li...@ruby-forum.com> wrote: > One thing I forgot to mention is at one stage of the form they'll need > to create children for records that were built in an earlier step. > Example (you create several children for the event in step 2 and in step > 3 you create children for those) > > -- > 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 unsubscribe from this group and stop receiving emails from it, send an > email to rubyonrails-talk+unsubscr...@googlegroups.com. > To post to this group, send email to rubyonrails-talk@googlegroups.com. > For more options, visit https://groups.google.com/groups/opt_out. > > > -- You received this message because you are subscribed to the Google Groups "Ruby on Rails: Talk" group. To unsubscribe from this group and stop receiving emails from it, send an email to rubyonrails-talk+unsubscr...@googlegroups.com. To post to this group, send email to rubyonrails-talk@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
