Hi, If the controller needs some more functionality it should be added to its class. If it doesn't belong there it shouldn't be part of its inheritance tree.
Give some concrete examples on what's missing and how would you use it. Maybe it's already achievable by some other means in the framework. Karol Dan Rossi-5 wrote: > > Hi there I meant a common class the controllers can extend to reuse some > functionality, ie getting the registries set in the bootstrap , etc. > Then it means its only editable in one spot. Maybe via a plugin ? > > Karol Grecki wrote: >> Dan >> >> You mean a class with some useful functions you can inherit from? Really >> bad >> idea. >> Besides controllers already inherit from from other class and bootstrap >> is >> just a file. >> Putting unrelated functionality into a single class is also not very OOP >> friendly. >> Instead, try using zend registry to store session and auth object. >> >> Karol >> >> >> Dan Rossi-5 wrote: >> >>> Hi there I was wondering if it was possible to have a baseclass for all >>> controllers, or a bootstrap, so thats its possible to contain reusable >>> methods for all controllers, IE session handling methods, authentication >>> etc. >>> >>> Let me know. >>> >>> >>> >> >> > > > -- View this message in context: http://www.nabble.com/project-baseclass-for-all-controllers-tf4203756s16154.html#a11961353 Sent from the Zend Framework mailing list archive at Nabble.com.
