Ralph,
Do you have any documentation or usage examples? Is there a proposal
document?
So does this class manage an array ('registry') of instantiated classes,
which are loaded on demand with a short name?
It seems very centered around plug-ins and helpers, I was (just) looking to
remove the necessity of 'requiring' model files in controller files.
I'm not sure if the two concepts are related, I don't think it's necessary
to store instantiated models in a registry?
On another subject, how are things going with Zend_Layout? Is there any
usable code available?
Thanks,
Glen.
Ralph Schindler wrote:
>
> Have a look at whats in the incubator, after seeing a repeated pattern
> in a few different components doing essentially the same thing, I
> proofed out what is called Zend_Loader_PluginLoader. This basically is
> the foundation for building Pluggable Architectures. Essentially, this
> allows the loading of non-include path code, at a specific prefixed
> namespace. Examples of this functionality can already been seen in the
> action helpers and view helpers.
>
> While it might not directly answer your question, its still worth a look.
>
> This also would be the foundations for having an action helper like a
> "ModelLoader".
>
--
View this message in context:
http://www.nabble.com/RFC---miscellaneous-enhancements-tf4743659s16154.html#a13575947
Sent from the Zend Framework mailing list archive at Nabble.com.
