Out of lack of time and some frustration I've come to the same stall. We had a similar situation to yours about three weeks back. We fiddled a lot and tried to work around the limitations given by Cake and PHP. I say and PHP because classes are inherently closed in PHP vs. Ruby where a plugin can re-open classes and add (to use your example) a bark () method/action to the DogsController.
Our lame but necessarily practical/quick solution was to give up on plugins. For everything that really has to hook into the core; seeing our system will stay in-house and new modules/plugins are mostly one off edge cases for customer requests we'll just take our core system and add to it. Not exactly an answer to your question but maybe a bit of our experience will bring up some ideas or nourish the discussion here. --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "CakePHP" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [email protected] For more options, visit this group at http://groups.google.com/group/cake-php?hl=en -~----------~----~----~----~------~----~------~--~---
