@@ -28,6 +28,12 @@ Creating a presenter is as simple as subclassing ActivePresenter::Base. Use the presents :user, :account end +In the above example, :user will (predictably) become User. If you want to override this behaviour, specify the desired types in a hash, as so: + + class PresenterWithTwoAddresses < ActivePresenter::Base + presents :primary_address => Address, :secondary_address => Address + end + === Instantiation Then, you can instantiate the presenter using either, or both of two forms. README.rdoc @@ -14,7 +14,12 @@ module ActivePresenter # class SignupPresenter < ActivePresenter::Base # presents :user, :account # end + # + # In the above example, :user will (predictably) become User. If you want to override this behaviour, specify the desired types in a hash, as so: # + # class PresenterWithTwoAddresses < ActivePresenter::Base + # presents :primary_address => Address, :secondary_address => Address + # end # def self.presents(*types) types_and_classes = types.extract_options! lib/active_presenter/base.rb 7576ebf25057bdab630831be8dcb170fa21bdc63 James Golick james@giraffesoft.ca http://github.com/giraffesoft/active_presenter/commit/983d7c186dc0c9b9968b25753b8aa4941dbc5e20 983d7c186dc0c9b9968b25753b8aa4941dbc5e20 2009-05-17T14:41:37-07:00 2009-05-17T14:41:37-07:00 doc the new behavior 818c6beab560882e2f37bda7dff3d261090737fa James Golick james@giraffesoft.ca