+1 It's a minor change to move an otherwise general purpose catchall type object that can be split out if needed. Is it so hard to believe svn users could find this useful? Should we see it as acceptable to add lists of directories to our include_path? Should we use make or phing to reorganise files after even svn update? Really? Pádraic Brady http://blog.astrumfutura.com http://www.patternsforphp.com
----- Original Message ---- From: Jim Scherer <[EMAIL PROTECTED]> To: fw-general@lists.zend.com Sent: Monday, February 26, 2007 3:37:09 PM Subject: Re: [fw-general] Request for feedback: moving Zend.php to Zend/Zend.php I agree with what Ralph and now many others are saying. +1. I'm a newbie, and like most programmers, do better with things that are logical and intuitive. The Zend class was a bit of a mystery to me until I read this discussion. A class named Zend meant nothing except that it was required to make the whole thing work. If it isn't a requirement and can be replaced by Zend_Registry, Zend_Loader, Zend_Debug I'd welcome that. And absolutely break my code and eveyone elses, it's pre-release. I've read from day one how you can use the entire framework or whatever components appeal to you. Including "Zend_Loader" or "Zend_Registry" doesn't lead me to believe that I'm getting the entire framework, but loading "Zend" does. To me, adding the "Zend" class to my project represented adding the framework in its entirety. That was my misunderstanding. If you were looking to add only a component or two, the "Zend" class might scare you off. I recognize that the documentation is being written to demonstrate how to use individual components, but I go to examples and index.php before documentation, and when I see 'include "Zend.php";' I think ut-oh, I have to include this giant file that represents the whole framework. Jim Ralf Eggert wrote: > > Hi, > > I personally think that the proposed renaming of the Zend class to > Zend_Framework is very misleading. I would expect that a Zend_Framework > class will set up the whole framework and not be just a funny > conglomeration of methods who did not find their way to a proper > component. > > Here are my suggestions: > > - move Zend::register(), Zend::registry(), Zend::isRegistered(), > Zend::initRegistry() and Zend::__unsetRegistry() to Zend_Registry > > - drop Zend::exception() and Zend::loadInterface() > > - move Zend::loadClass(), Zend::loadFile() and Zend::isReadable() to > a new Zend_Loader class > > - as suggested by others, move Zend::dump() to Zend_Debug > > - the only method I am not sure about yet is Zend::compareVersion() but > I bet we will find a solution for this as well > > Like others I would also suggest to implement these changes before the > 0.9.0 beta release gets launched. > > Best Regards, > > Ralf > > > -- View this message in context: http://www.nabble.com/Request-for-feedback%3A-moving-Zend.php-to-Zend-Zend.php-tf3290016s16154.html#a9160964 Sent from the Zend Framework mailing list archive at Nabble.com. ____________________________________________________________________________________ Do you Yahoo!? Everyone is raving about the all-new Yahoo! Mail beta. http://new.mail.yahoo.com
