Add constants; refactor View classes and tests to use them; refactor out handler_guts

[maypole.git] / doc / StandardTemplates.pod

diff --git a/doc/StandardTemplates.pod b/doc/StandardTemplates.pod
index dd76189fba0e5bcc1f162872ae7cdccb73956ecf..e5eb9f06b2f32aeaebde9438469bb90301b9b2d1 100644 (file)
--- a/doc/StandardTemplates.pod
+++ b/doc/StandardTemplates.pod
@@ -252,29 +252,7 @@ macros as we come across them.
 
 =head3 F<view> 
 
-The C<view> template takes some objects (usually just one) from
-C<objects> and displays the object's properties in a table. It gets
-the displayable form of a column's name from the hash returned from
-the C<column_names> method:
-
-    <TR>
-        <TD class="field"> [% classmetadata.colnames.$col; %] </TD>
-
-One interesting macro used in this template is C<maybe_link_view>:
-
-        maybe_link_view(item.$col);
-
-This tests whether or not the returned value is an object, and if so,
-creates a link to a page viewing that object; if not, it just displays
-the text as normal. The object is linked using its stringified name;
-by default this calls the C<name> method, or returns the object's ID
-if there is no C<name> method or other stringification method defined.
-
-The C<view> template also displays a list of other objects related to the first
-one via C<has_many> style relationships; this is done by calling the
-C<related_accessors> method - see L<Model/related_accessors> - to return
-a list of has-many accessors. Next it calls each of those accessors, and
-displays the results in a table.
+=template view
 
 =head3 F<edit>
 
@@ -307,3 +285,4 @@ The C<search> template argument is used to distinguish between the two cases:
     <h2> Listing of all [% classmetadata.plural %]</h2>
     [% END %]
 
+=head1 Customizing Generic CRUD Applications