5 The C<view> template takes some objects (usually just one) from
6 C<objects> and displays the object's properties in a table.
14 [% FOR item = objects %]
15 [% SET string = item.stringify_column %]
16 <h2> [% item.$string %]</h2>
21 <TR><TD class="field">[% classmetadata.colnames.$string %]</TD><TD> [% item.$string %] </TD></TR>
23 FOR col = classmetadata.columns.list;
24 NEXT IF col == "id" OR col == string;
25 NEXT UNLESS item.$col;
32 It gets the displayable form of a column's name from the hash returned
33 from the C<column_names> method:
38 <TD class="field"> [% classmetadata.colnames.$col; %] </TD>
43 IF col == "url"; # Possibly too much magic.
44 "<A HREF="; item.url; "> "; item.url; "</A>";
49 #One interesting macro used in this template is C<maybe_link_view>:
51 maybe_link_view(item.$col);
56 This tests whether or not the returned value is an object, and if so,
57 creates a link to a page viewing that object; if not, it just displays
58 the text as normal. The object is linked using its stringified name;
59 by default this calls the C<name> method, or returns the object's ID
60 if there is no C<name> method or other stringification method defined.
76 The C<view> template also displays a list of other objects related to the first
77 one via C<has_many> style relationships; this is done by calling the
78 C<related_accessors> method - see L<Model/related_accessors> - to return
79 a list of has-many accessors. Next it calls each of those accessors, and
80 displays the results in a table.
89 button(item, "delete");