I'm making an application specific template from the default
templates based on the content of the factory templates and it's
pretty evil.
The default edit template looks like this:
[% FOR col = classmetadata.columns;
NEXT IF col == "id";
'<label><span class="field">';
classmetadata.colnames.$col; ":</span>";
item.to_field(col).as_XML;
# etc.
%]
I want to lay out my form myself in the template. There may be a
neater way of doing it, but the default template encourages serious
uglieness:
<label><span class="field">[% item.project.name;
# this seems quite reasonable
%]
</span> [%
item.to_field(classmetadata.columns.0).as_XML;
#yuck why can't I reference by the name of the column?
%]
It would be better to be able to coerce classmetadata.columns into a
hash so I could refer to classmetadata.columns by column name.
Or will this be fixed in 2.11?
-------------------------------------------------------
This SF.net email is sponsored by: Splunk Inc. Do you grep through log files
for problems? Stop! Download the new AJAX search engine that makes
searching your log files as easy as surfing the web. DOWNLOAD SPLUNK!
http://ads.osdn.com/?ad_id=7637&alloc_id=16865&op=click
_______________________________________________
Maypole-devel mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/maypole-devel
