Hi Arik, The idea is not to replace xDebug, but to offer an additional and built-in tool to debug the request/response process of the framework. Also, you need access to the server to install xDebug, and not everyone has this privilege.
Here is a typical scenario: You are asked to make some changes to a view script used by the LatestController of the "Blog" application. Instead of going to the controller and analysing the code, you go straight to the debug page, e.g.: Make the request: http://www.blog.com/latest Get info: http://www.blog.com/debug DebugController is just an action controller that renders a view script and displays the info captured by Zend_Debug, it can output it as HTML or XML. This page will tell you everything you need to know about the request you've just made. A user-friendly description of everything that happened inside Zend_Controller. For example: Returns info stored in the request object, info of the router (which routes have been injected into the controller), executed queries, and a list of rendered templates and the location of those files, so you know what to edit and where to find it. Personally, when working with different sites, I spend a lot of time visiting the /debug page, and it saves me a great deal of time. I don't need to open massive controllers or try to figure out what other developers did to find out what the controller is doing, what queries is running, or templates using, etc. Fed Arik Fraimovich wrote: > > I completely agree that debugging functionality is essential for proper > development and for understanding of a project you take over. But why not > use something like xDebug or ZendDebugger? > > Arik > > On Dec 27, 2007 12:15 AM, Federico Cargnelutti <[EMAIL PROTECTED]> > wrote: > >> >> Hi, >> >> Does anyone know if there are any plans to add new functionality to the >> Zend_Debug class? IMO this class has a lot more to offer. >> >> I always found inspirations in the eZ Components library, and the first >> thing I did when I got my hands on the ZF was to add a similar component >> to >> http://ezcomponents.org/docs/tutorials/Debug ezcDebug to the framework. >> >> Imagine a Debugger that provides the user with valuable information, such >> as >> action controllers executed, parameters passed, views rendered, location >> of >> files, etc. And allow the user to write debug messages, and measure >> execution times. Basically to keep track of what's going on in the >> request/response process. It will of course depend on Zend_Log and other >> classes. >> >> In the last media agency I worked for, they had an action controller >> called >> DebugController, that could only be accessed by a range of IP addresses. >> This page would give you all the information of the last 6 requests made >> by >> an IP address (actions, params, queries executed, etc). It's such a >> useful >> tool, specially when you take over a project that don't know anything >> about, >> and you want to know exactly what the framework is doing behind your >> back. >> >> Has anyone implemented something similar? Are there any plans to >> implement >> something like this to the ZF? >> >> Thanks and happy holidays :) >> >> Fed. >> >> >> >> >> >> >> -- >> View this message in context: >> http://www.nabble.com/Zend_Debug%2C-eZComponents-style.-tp14507061s16154p14507061.html >> Sent from the Zend Framework mailing list archive at Nabble.com. >> >> > > -- View this message in context: http://www.nabble.com/Zend_Debug%2C-eZComponents-style.-tp14507061s16154p14511366.html Sent from the Zend Framework mailing list archive at Nabble.com.
