I propose in 2.12 or something, (I use it now) that the Controller or
Maypole Request class and/or object should be stashed in the model.
Currently I set the controller class as class data in each model in
the "setup_model_class" hook. . Then i access it like
$class->controller->config{uri_base} and what not.
I found this very useful when different maypole apps mingle with each
oother. For instance when an Employee has_a Customer and they are
controlled by two different Maypole apps and you want to bounce around
between the two. . Having access to the controller for a class is
crucial to linking to it. Also theres other useful configs in classes
controller.
Any one have any objections to this? Any ideas on implementation?
Should the whole object be passed in right before the model is
processed perhaps? Or should the class name and thus class data be
sufficient?
--
pjs
-------------------------------------------------------
This SF.Net email is sponsored by xPML, a groundbreaking scripting language
that extends applications into web and mobile media. Attend the live webcast
and join the prime developer group breaking into this new coding territory!
http://sel.as-us.falkag.net/sel?cmd=lnk&kid0944&bid$1720&dat1642
_______________________________________________
Maypole-devel mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/maypole-devel
