I have a person table and an event table (and many mores, but these two illustrates my problem) A person has many events I have a person resource and an event resource to manage the records in the tables Now I also want to manage person and events together in a more user friendly way.
My problem is now how to design the application ? 1. Should I have one person controller and one person resource, one event controller and on event resource and add a set of actions to the person and/or event controller to handle the user friendly management of persons and events ? 2. Should I have specifc controllers and resources representing different representations of persons and events, as the user friendly integrated representation and the table representation, each (if possible) limited to the seven basic actions (index, show, new , edit etc) ? E.g a person controller, an event controller and a person-event controller and corresponding resources! 3. Should I have a specific person-event controller with many specific actions, in addition to the person and event controller, that uses the same person and event resources? --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
