To add to that.. Rick, that type of parent/child functionality in models is exactly what I have envisioned but with controllers. So if that means instead of putting everything in the /app/models/customer/ directory, there exists a parent model and then child models under the directory of the parent class name, I'm all for that. To revise my first posting then:
routes: map.resources :customers, :namespace => true do |customers| customers.resources :tags customers.resources :notes end or map.resources :customers, :namespace => :customers do |customers| customers.resources :tags customers.resources :notes end or map.namespace :customers, :resource => :customers do |customers| customers.resources :tags customers.resources :notes end controllers: /app/controllers/customers_controller.rb /app/controllers/customers/notes_controller.rb /app/controllers/customers/tags_controller.rb ..something to that effect. Regards, Peter --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
