Sharagoz -- wrote: > If your controllers are getting fat it might be an indication that you > are putting a lot of the logic in the wrong place and not using the MVC > architecture the way its ment to be used. "Skinny controller, fat model" > is the practice most try to follow. The "calculation detail" usually > belongs in a model.
Are you suggesting to put "everything" into a model, even if it's not related to a database object? So to also put classes into the the app/models directory, which are not of type ActiveRecord::Base ? Just as an example: I'm using the FasterCSV gem, in order to read uploaded CSV files into a hash table structure, and do a lot of post-processing with this data. I thought it would be more logical to create a separate class in the rails lib directory, and then use its methods from within my controller. -- Posted via http://www.ruby-forum.com/. -- 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.
