I like this idea. Shekar C Reddy <[EMAIL PROTECTED]> wrote: Bill, I guess this was discussed earlier and much desired. However, to work around the exception, could we look into renaming the Zend class to something like: Zend_Main or Zend_Public or Zend_Shared or Zend_Common or Zend_General or Zend_Base or Zend_Core or Zend_Standard... so the name of the file would be just: Main.php/Public.php/Shared.php/Common.php/ General.php/Base.php/Core.php/Standard.php/etc sitting in the Zend folder? What do others think? Main/Public/Shared/Common/General? Votes? Ideas for more names...? Regards,
On 2/25/07, Bill Karwin <[EMAIL PROTECTED]> wrote: Please take a look at http://framework.zend.com/issues/browse/ZF-958 We propose to move Zend.php to <zf-home>/library/Zend/Zend.php. The class name would continue to be 'Zend', and we're not suggesting changing any methods within the class. Therefore no usage of this class would change. The only change in your application would be that you need to change this: require_once 'Zend.php'; To this: require_once 'Zend/Zend.php'; Alternatively, you could add the 'Zend' directory to your include_path. The benefit of this change is to simplify integration of a Zend Framework tree in an application tree. You could use svn externals, for instance. The disadvantage is that it does not follow the ZF convention that class names always match the physical location of the class file. But this is the only class that needs to be an exception to this convention. I volunteer to make this change. I'll update other classes in the ZF tree. I'll write a note in the manual to tell users what they need to do. I'll write a docblock in Zend.php acknowledging that it is an exception to the class-to-location convention. If there are no strong objections, I'll make this change. Regards, Bill Karwin --------------------------------- Food fight? Enjoy some healthy debate in the Yahoo! Answers Food & Drink Q&A.
