> You should put it under lib/contact.rb if you want to follow the > general convention. Really? It seems to me that Contact (ActiveRecord subclass or not) would be a legitimate model object in a MVC system. I could see putting some utility classes and stuff that doesn't really have a place in MVC in the lib folder. That seems perfectly reasonable to me. Not everything can be pigeon-holed into any specific design pattern.
So are you saying that any model object that is not subclassing ActiveRecord::Base should not be kept inside the app/models folder? Even when it is obviously a model object managing data, even when that data may not be persisted to a database table. I'm just looking for some clarification here. Is this just a developer preference on how to organize classes? Or, are their issues surrounding keeping non-ActiveRecord model objects in the /app/models folder? Pratik Naik wrote: > You should put it under lib/contact.rb if you want to follow the > general convention. ...snip... > Cheers! > - Pratik > http://m.onkey.org -- 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 -~----------~----~----~----~------~----~------~--~---
