As no one else has added, I'll give my two pennies worth - "extended controller takes longer to process because of having to go up the chain. I don't know how much overhead this really is, though."
I wouldn't worry about it, Cake's very OO and subclassing like this is standard OO practice - go with the flow, not against it! If you're still concerned, the Decorator design pattern can be useful for stopping overly deep class families (check Wikipedia, Google). "I'm wondering though, is there a way to get the parent's views such that I only have to have a view in one place, such as 'article' instead of duplicating views for content, announcement and event? " Maybe I'm not getting you, but could you not just create some fields in the top level class, or app_controller, which can be accessed from all subclasses and tell them what folder to look into for the view? Or you can put repeating view stuff in different layouts, seperating them like that, or in Elements... take your pick! --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Cake PHP" 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 -~----------~----~----~----~------~----~------~--~---
