I'm starting a list of Incompatibilities and fixes for Maypole with
Class:;DBI 3.XXX.
1) In the template name macros:
IN the display_line macro :
accessor_name is deprecated. Use "accessor_name_for" . Also you
now have to pass a column obj as the arg to it. If you have Related
accessors (for has_many or might_have cols ) or just another method ,
you have to take that into account. Here is a patch for the two cases
in the IF ELSEIF sequence that makes up that macro:
....
# url check
# string check
ELSIF ( col_obj = item.find_column(col) ) ;
# A real column check handling customized accessor names
accessor = item.accessor_name_for(col_obj);
maybe_link_view(item.$accessor);
ELSE;
# Everything else not colums like accessors to related objects
# or some other method that returns data you want in a cell in the
# listing table. Try it it is fun*. ;)
maybe_link_view(item.$col);
END;
....
* for this to be fun you need to make a table heading show up for the
non column method in your list_columns. Under standard maypole
templates you can do this by putting an entry in the "column_names"
list for this method. Or you can edit the list template (Better idea
because then while you're there you can make the heading link created
for you method not break your app. See list table headings bug report.
)
cheers
--
pjs
-------------------------------------------------------
This SF.Net email is sponsored by:
Power Architecture Resource Center: Free content, downloads, discussions,
and more. http://solutions.newsforge.com/ibmarch.tmpl
_______________________________________________
Maypole-users mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/maypole-users
