Topic: Control Panels and large number of contained models
How do you like to structure the logic behind control panels -- ie a view that exposes CRUD+extras(order up/down/etc) for a wide range of interacting models. Typically speaking you'd have lots of "somethings" -- "events" or "trips" or whatever -- that have lots of pieces to configure and you want to have most of the operations reachable in a small number of clicks. All of these component models typically "belong_to" the master element, so you'll have to be passing around/sessioning the container's id.
Do you "just" create all the seperate controllers for each model and then have tons of url_for(:controller=>, ....), and then have all the actions redirect back to the main panel? Do you fold all the actions for the cotnained entities into the "master" controller so you simple actions/redirects? Other options that you're happy with?