Google seems to indicate that one may simply mixin (Is that the correct Ruby terminology.) parts of ActiveModel into any class as one sees fit. For example:http://yehudakatz.com/2010/01/10/activemodel-make-any-ruby-object-feel-like-activerecord/ If memory about the way inheritance works in Ruby serves me we should be able to do something like that, without even needing to derive from ActiveModel directly. Though in the case of a Rails application one would probably just create a stub class that derives from ActiveRecord::Base stick the common methods in there and then subclass that class since ActiveModel does not include the database related functionality.
-- You received this message because you are subscribed to the Google Groups "Ruby on Rails: Talk" group. To view this discussion on the web visit https://groups.google.com/d/msg/rubyonrails-talk/-/SGFNOFFjZGpKOTBK. 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.
