X-Git-Url: https://git.decadent.org.uk/gitweb/?a=blobdiff_plain;f=lib%2FMaypole%2FManual%2FInheritance.pod;h=bff339db3bd467b82f5cf6c59d90c3df1c573026;hb=dbaa73455bdbb63e09581e807d0ae87ec92dd087;hp=6c6c6b77eba53e34624cf88766ec64bb52017412;hpb=6c19a422c2c4bc3457f311ffc0403b8644690074;p=maypole.git

diff --git a/lib/Maypole/Manual/Inheritance.pod b/lib/Maypole/Manual/Inheritance.pod
index 6c6c6b7..bff339d 100644
--- a/lib/Maypole/Manual/Inheritance.pod
+++ b/lib/Maypole/Manual/Inheritance.pod
@@ -30,11 +30,11 @@ application.
 
 =back
 
-=head1 A standard Maypole application
+=head1 Structure of a standard Maypole application
 
-A minimal Maypole application (such as the Beer database) consists of a 
-custom driver class (BeerDB.pm), a set of auto-generated model classes, and a 
-view class: 
+A minimal Maypole application (such as the Beer database example from the
+L<Maypole> synopsis) consists of a custom driver class (BeerDB.pm), a set of
+auto-generated model classes, and a view class:
 
 
            THE DRIVER
@@ -92,9 +92,10 @@ itself in the hierarchy, but this was unnecessary).
 
 =head2 Who builds the model?
 
-First, remember we are talking about the standard, unmodified Maypole here. 
-It is possible, and common, to override some or all of this stage and build a 
-customised model.
+First, remember we are talking about the standard, unmodified Maypole here. It
+is possible, and common, to override some or all of this stage and build a
+customised model. See below - An advanced Maypole application - for one
+approach. Also, see L<Maypole's|Maypole> C<setup_model()> method. 
 
 The standard model is built in 3 stages. 
 
@@ -110,10 +111,12 @@ Next, C<Maypole::setup> B<unshifts> L<Maypole::Model::CDBI> onto the C<@ISA>
 array of each of these classes. 
 
 Finally, the relationships among these tables are set up. Either do this
-manually, perhaps with the help of L<Class::DBI::Relationship>, or use
-L<Maypole::Plugin::Relationship>. In the latter case, you need to set up the
-relationships configuration before calling C<setup()>.
-
+manually, using the standard L<Class::DBI> syntax for configuring table
+relationships, or try L<Class::DBI::Relationship> (which you can use via
+L<Maypole::Plugin::Relationship>). If you use the plugin, you need to set up the
+relationships configuration before calling C<setup()>. Be aware that some people
+like the convenience of L<Class::DBI::Relationship>, others dislike the
+abstraction. YMMV. 
 
 =head1 An advanced Maypole application
 
@@ -270,6 +273,20 @@ calls on the underlying model.
 Whatever label you prefer to use, this approach provides for clear separation of
 concerns between the underlying model and the web/user interface, and that's
 what it's all about.
+
+=head1 Advanced applications - building the model by hand ** TODO
+
+- using Maypole::Model::CDBI::Plain or Maypole::FormBuilder::Model::Plain
+- setup_model() and load_model_subclass()
+- cutting out all those separate paths to CDBI - they're confusing 
+
+
+=head1 Method inheritance ** TODO
+
+More description of Perl's left-to-right, depth-first method lookup, and where
+it's particularly important in Maypole.
+
+
           
 =head1 AUTHOR