The Zend Framework community is currently reviewing the proposal process. This is a good thing, considering that the community has grown quite a bit in the last year. I remember that one of the questions asked in the Q&A session for Zend Framework 1.0 was:
Q: Are there any plans for making Zend_Debug fancier? In a way of looking like Xdebug.
A: No, currently there is no specific proposal for enhancing the Zend_Debug class.
Hopefully, the new proposal system will help enhance some of the existing components, including Zend_Debug, and speed up the development process of new ones. In the meantime, if you think you need more diagnostic information, I’d recommend you download PHP_Debug. If you are familiar with Symfony, then you’ll be happy to know that PHP_Debug provides a similar Web toolbar.
The Definitive Guide to Symfony:
“During both the development and deployment phases, developers require a consistent stream of diagnostic information in order to determine whether the application is working as intended. This information is generally aggregated through logging and debugging utilities.”
That’s exactly what a developer needs when developing a Web application. I think Zend Framework should provide diagnostic information by default. At the moment there’s no way to know if an action was forwarded to another Action Controller, if an Action Controller executed a pre or post-dispatch method, if a model executed the same query twice, or if a variable was registered with the Request object.
By the way, make sure you don’t miss the next Big Zend Framework Q&A session.
9 PHP Debugging Techniques You Should Be Using, by Adam Charnock.