On 6/11/07, Trevor Squires <[EMAIL PROTECTED]> wrote: > > > > With that in mind, consider this contrived example application: > > map.resources :houses do |house| > house.resources :walls, :has_many => :damages > house.resources :windows, :has_many => :damages > house.resources :doors, :has_many => :damages > house.resources :damages > end > > The :damages resource appears four times, touching every other > resource and the entire application seems to hinge on the concept > Damage. > > However, in terms of template and controller lines, Damage probably > (simplistically) only accounts for about 20% the application total.
This is a bit off topic, but could anyone point me at some discussion about what the damages controller would look like in this situation. How much, and what code goes into determining what objects are to be setup? For example. I have a situation where I have :books, :has_many => :clips /books/1/clips This is fine, I can deal with this, but I would also like another part where I can look into others books /public/username/books/1/clips But I don't really know what the controller should look like to set this up. Any links would be great. Cheers --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Ruby on Rails: Core" 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-core?hl=en -~----------~----~----~----~------~----~------~--~---
