>>> Try classmetadata.name.<method> ?
>>
>> No luck. I tried classmetadata.customer.types, request.customer.types,
>> request.model.types . I'm guessing its something simple like that but
>> can't
>> find it in the docs.
>
>
> Uhm, I'm sorry, my template toolkit knowledge is limited, but
> $classmetadata->{name} contains a reference to the actual class in use.
I don't think so. From Maypole/View/Base.pm:
$args{classmetadata} = {
name => $class,
$class is a string giving the name of the class, not an object. In TT at
least, you can't use a method of a string!
> This works with the mason view:
> <% $classmetadata->{name}->table %>. However, classmetadata.name.table
> returns nothing in TT. So the data you crave is there, but I'm not sure
> how you can get to it.
BTW, in looking at this I noticed there seem to be some inconsistencies
in the docs. In the Workflow doc, the table element of classmetadata is
not mentioned. In the 'Maypole View Classes' doc the name element is
called class. Both docs mention an element called description but don't
explain that it isn't provided by the framework or explain how you
should/can provide it.
Cheers, Dave
_______________________________________________
maypole mailing list
maypole at lists.netthink.co.uk
http://lists.netthink.co.uk/listinfo/maypole
This archive was generated by hypermail 2.1.3 : Thu Feb 24 2005 - 22:25:56 GMT