Hey folks, Nobody faced this issue before? I am surprised. Or was my description not very clear? In any case I am doing the entire thing in one model then see how it works out.
On Thu, Dec 20, 2012 at 11:49 AM, why-el <[email protected]> wrote: > Hey fellas, > > I am trying to put together a small app to help my university accept > applications for one of its summer programs. Currently, they send you an > application, you print it, you fill it, scan it, then send it back! We > can't tolerate this in a world of Rails. > > Anyway, so the giant form has personal information section, language > information section (The biggest part, about a page and a half, this checks > your current level of Arabic), and a track information section that > presents you all tracks and their fees and schedules for you to choose > from. I am putting each section into its own step so the form will navigate > three steps. > > Now, my question is, wouldnt it make more sense to break these into > different models? One "application" model will be too big. For some reason > I can't reason about how to do this. What would the other models be? Does > it make sense to have a "language information" model that belongs to some > student's application? > > Thanks for your help. > > -- > 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]. > To view this discussion on the web visit > https://groups.google.com/d/msg/rubyonrails-talk/-/8tf3VBJS5kwJ. > For more options, visit https://groups.google.com/groups/opt_out. > > > -- Mohamed Wael Khobalatte -- 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 https://groups.google.com/groups/opt_out.
