> > I think I'm sold on your idea of setting template_args. It's simple and
> > fairly
> > intuitive and it requires the least amount of work. For more advanced
> > requirements you can still use a custom model/view.
> >
> > So, unless anyone objects, in 2.05 you'll be able to set
> > $r->template_args->{classmetadata}{foo} and the view class won't attempt
> > to
> > set its own classmetadata.foo.
> >
> > It'll also makes it easier to extend classmetadata with properties of your
> > own.
>
> I agree. I think this is a good way to allow for more flexible
> classmetadata without changing the actual API.
>
Just to clarify, Maypole always had the flexibility. It just does it
inefficiently (but easily) -- makes all default classmetadata and other vars
before it even looks at template_args to see if you override them.
=====
pjs
__________________________________
Do you Yahoo!?
The all-new My Yahoo! - Get yours free!
http://my.yahoo.com
_______________________________________________
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:57 GMT