described as a Presentation Model (see below). In complex Maypole applications,\r
it is good practise to separate the domain model (the 'heart' of the\r
application) into a separate class hierarchy (see\r
-L<Maypole::Manual::Inheritance).\r
+L<Maypole::Manual::Inheritance>).\r
\r
The distinction is relatively unimportant when using Maypole in 'default' mode - \r
i.e. using L<Maypole::Model::CDBI>, and allowing Maypole to autogenerate the \r
outweighed by the heuristic advantage of separating different layers into\r
separate class hierarchies.\r
\r
+=back\r
+\r
=head3 Presentation Model\r
\r
This pattern more accurately describes the role of the Maypole model.\r
the role of the C<vars()> method on L<Maypole::View::Base>, which transmits the\r
new values to the templates.\r
\r
-=back\r
-\r
=head1 AUTHOR\r
\r
David Baird, C<< <cpan@riverside-cms.co.uk> >>\r