--- Simon Flack <sf at flacks.net> wrote:
> >
> >>I agree. The most significant place that the table name is used over the
> >>moniker() is the request url. That's a pretty significant change though.
> >
> >
> > Hmm. Why's that? Do you mean for reasons of backwards compatbility, or
> > in terms of technical implementation?
>
> Mainly for reasons of backwards compatibility. It won't be too hard to
> get it working, but we'll need to update most of the factory templates
> and some of the documentation. The feedback on this so far is positive,
> so I've put it on the todo list.
>
> > I think it's quite an important change, and hadn't actually realised
> > Maypole dispatched purely based on table names!
Thanks to tony, there is now very compelling reason why table should NOT be
used for Directories and URLS. It is clear (at the moment to me) a class method
(and perhaps same method at that) should be used to determine these.
But for the life of me, WHY UNIVERSAL::moniker ??? By using that you take the
Universe out of it and effectively make it "UglyMaypoleInternal::moniker". It
becomes useless for human consumption and something solely for computer
consumption (unless computers and humans agree on what something should be
called). It contradicts the Universe::moniker doc. It means all the templates
have to be changed. It means you really don't want to override it if you can
help it.
A more appropriate method would be Maypole::Model::Base::maypole_moniker. This
would effect fewer changes on Maypole (docs, templates, internals alike) and be
more intutive to users trying to figure out their URLS and Directories.
=====
pjs
__________________________________
Do you Yahoo!?
Yahoo! Mail - You care about security. So do we.
http://promotions.yahoo.com/new_mail
_______________________________________________
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