> You don't want to cram too much into your controllers either. The design
> philosophy is "skinny controllers, fat models."
>
> http://weblog.jamisbuck.org/2006/10/18/skinny-controller-fat-model
> --
> Posted viahttp://www.ruby-forum.com/.
Wow! Excellent reference. The role of models has always been elusive
to me. It has always appeared to me that a model was something to be
used only with a database. How did I come to that conclusion? Models
descend from ActiveRecord::Base. A cursory reading of your reference
seems to indicate that models are much more. One thing that seemed to
leap out at me was that a model could be a mechanism for passing data
which was common to all views. Anyway, I have to study this in more
detail and do some playing with it. Thanks for the input.
... doug
--~--~---------~--~----~------------~-------~--~----~
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
-~----------~----~----~----~------~----~------~--~---
