Hi Chris, Your model classes can inherit from an Estimate class, passing request, etc is likely to be a sign of something wrong in your design.
So you have an estimate class with a bunch of general methods, that take nice named parameters, that you can unit test outside of maypole. Then your particular estimate subclasses, i.e. Estimate::Painting, inherit from Estimate like so : package Estimate::Painting; use strict; use warnings; use base qw( Maypole::Model::Whichever Estimate ); ... This kind of setup works nicely for me - I have a nice working set of model classes and then provide the actions in a subclass so that I can unit test the main classes first before integrating them in Maypole. You may find that perl -cw Estimate::Painting will fail on the attributes, instead perl -cw the Maypole controller class i.e. YourApplication.pm which sets up each model class, at which point they are all compiled. That works fine. regards, Aaron. -- http://www.aarontrevena.co.uk LAMP System Integration, Development and Hosting ------------------------------------------------------------------------- This SF.net email is sponsored by: Splunk Inc. Still grepping through log files to find problems? Stop. Now Search log events and configuration files using AJAX and a browser. Download your FREE copy of Splunk now >> http://get.splunk.com/ _______________________________________________ Maypole-users mailing list Maypole-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/maypole-users
