Hi,
I like this approach but I have a question: in the example you give of
extending base controllers I am wondering how you deal with
namespaces? Do you add a prefix to the base controler for example?
Thanks
Dan
On 23 Dec 2009, at 07:02, Simon R Jones
wrote:
hi Paul,
We have the sa
AJ asked me to post snippets of my "hook" system.
Well, I try to keep this simple:
My Bootstrap class (defined by Zend_Application) has following static
method.
I'm sure it can be made better but it seems to work for me.
/**
* Call hook in modules (Note! methods must be static!)
*
* @param
Totally agree with you. I actually implemented something very similar
on my last project, having reusable modules in the library that were
added as svn externals. I'm about to start a new project and was
wondering if I made the right decision to put it in the library folder.
Sounds like we a
Hi,
I have the following setup:
1. My application, has the usual stuff, "core" modules, controllers etc etc.
2. Library, Zend, ZendX, PHPExcel etc. and my own library-level classes.
3. site-specific folder. this one has application.ini, cache folder, search
index. etc.
everything to do with t
hi Paul,
We have the same requirement at Studio 24: basically wanting to store
a re-usable module which has core, usually non-editable code which can
then be extended/customised for a client project.
I agree the normal ZF modules don't really cover this use case. At
present we place this
I know this has been discussed before, but was is the best way to handle
external modules?
I not asking for a place to find modules or for ZF to have a site
dedicated to modules, just want to know what the standard is for
installing a module into your existing system.
To me the library directo
