However, specifying the default prefix as Zend_View_Helper for helpers
placed under views/helpers/ doesn't make much sense since Zend prefix
is occupied by the official Zend Framework components, so if I wanted
to place helpers there at all (it's more likely that I have my own
library), I think the best would be to use nothing as default
namespace.

Technically, it should be Default_View_Helper_HelperName in the default namespace. That to me, seems ideal since the "module-name" for that branch would be default/. Of course, I am not a huge fan of the word "Default" anyway, but nothing has really emerged as a better replacement.

Another thing is that, if there's a directory to place my
site-specific view helpers and filters, why isn't there a place for my
action helpers and plugins? It would be very convinient to use these
instead adding my plugins and helpers manually in the bootstrap -- and
since I don't have extended/own classes in my library, only
plugins/helpers/filters I could eliminate the need of that directory.

I actually use modulename/controllers/actions/ as a place for my controller specific Action Helpers. I have also at times used modulename/controllers/plugins/ for plugins that get registered by my AbstractController (upon that module being dispatched). Most times though, you probably wont be writing module specific Controller Plugins since alot of their "localized" functionality can also be hooked into by the Action Helpers.

I think at 1.1 time, a pretty standard and full featured site can be built without creating any "library" code.

-ralph

Reply via email to