Oh, I also want to add that Admins will manage Users too, not just Companies and Themes. So there is a conflict where Companies can create/edit/delete Users and use/not use the same controller. There is also potential route conflicts unless you use nested resources.
I also want to add that Admins can do some things to users, but Company users can do other things. It's not just a subset - but the views and actions and forms will be somewhat different. That is why I am having difficulty figuring out the routes, what the controllers should be, and what to generalize and what to keep separate. -- 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 rubyonrails-talk@googlegroups.com. To unsubscribe from this group, send email to rubyonrails-talk+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/rubyonrails-talk?hl=en.
