I always thought that Default_ was the recommended namespace for everything
under the application/ tree that's part of the default module, and that
Application_ was becoming the standard for library/application/. Have I
always been mistaken or has this changed recently?
This always made sense to me:
application/
controllers/ → *Controller
forms/ → Default_Form_*
models/ → Default_Model_*
modules/
admin/ → Admin_*
blog/ → Blog_*
library/
Zend/ → Zend_* (if ZF is not in global include_path)
MyCompany/ → MyCompany_* (shared components within company, etc)
Application/ → Application_* (components specific to application that
don't fall under modules, such as a custom Action Helper)
Now that application/ maps to Application_ (which makes sense from a
directory naming perspective, but not so much from a modular perspective),
is the recommendation that you give your application-wide library an
application-specific namespace?
*CM* : http://cmorrell.com/ — @inxilpro <http://twitter.com/inxilpro>
On Fri, Mar 26, 2010 at 1:29 PM, Matthew Weier O'Phinney
<[email protected]>wrote:
> "Application" is what we specify as the default for resources under the
> "application" tree -- but even this is fully configurable, and I'd
> recommend using one that's project specific.
>
