If eliminating Zend.php is not possible, how about renaming it to something like Zend_Base so it can be moved into the framework-root (library) folder?
On 10/6/06, Ralph Schindler <[EMAIL PROTECTED]> wrote:
> The real reason to remove is is that it does not belong. It is a
> mishmash of Registry, Loading, and Debug that will only cause global
> dependencies down the road that will make things worse -- not better.
>
> I second the motion to remove it.
>
+1 here on reorganizing Zend.php into more logical components.
From an outsiders perspective, I would not know what if anything to
expect from the Zend.php file by its placement in the root. While much
the framework is shaping up, sticking with a loose coupling, a simplicty
and common sense approach, I think some refactoring can be done on
Zend.php to fit in with the growing body of code the ZF is.
My suggestions are:
* To remove Zend::registry()/register()/isregistered(), and allow
Zend_Registry handle its own business.
* Move dump() to something like Zend_Debug::dump().. also add
functionality to allow Zend_Debug hook into things like xdebug, etc.
* Move loadClass/loadFile/loadInterface/isReadable to a Zend_Load
class. I am not sold on the isReadable() implementation, and am not
completely sold on if isReadable is needed in loadFile()..
Perhaps the load stuff can stay in Zend.php, this would make Zend.php
the 'Framework Bootstrap file', and its purpose would be clear cut.
But I do think some logic should be added to this file.. in an
existential way.. why is it here?
-ralph
