The data is already there, let's take the Request Object for example. All you need to do is inject it into Zend_Debug and the component does the rest. Of course you can have an enable() and disable() method as well, you might want to disable it before or after an action controller is executed. But once you pass the request object, it should be enabled by default.
So, if you inject the log, request and profiler objects, you are ready to go: public function enable() public function isEnabled() public function disable() public function setRequest(Zend_Controller_Request_Abstract $request) public function setLog(Zend_Log $log) public function setDbProfiler(Zend_Db_Profiler $profiler) public function setDependencies(Zend_Di_Container $dependencies) public function log($message, $priority) public function write() public function setAuth(Zend_Debug_Auth_Interface $auth) public function getFileContents() public function dump($var, $label=null) ... - Fed Hi, I see what you mean. But doesn't that mean that some code for collecting debug information has to run all the time? Or you activate it before-hand in order to start collecting the debug information? Arik -- View this message in context: http://www.nabble.com/Zend_Debug%2C-eZComponents-style.-tp14507061s16154p14519903.html Sent from the Zend Framework mailing list archive at Nabble.com.
