I wrote really similar debug class for my company.
It helps debug a lots. but, adding debug interface at the end of document breaks design too much such as iframe-ed pages or popup-ed pages. and debugging is hard on pages which is redirecting.
so, I changed my debug class by writing every log data on /tmp and it dosen't require calling function like writeDebug(). it uses exit_handler
.
so, whenever programmers need to debug, they can simply press shortcut button on their debug pages.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Well it could be achieved. I think to a new function , debugLog() , which would be called at the place of DebugDisplay or/and a new attribute could define the type of the output. For the Pear version, i will use Pear::Log of course.
It is not the first someone ask me to have the possibility to save debug as logs, so i think it will be a part of the next version. I will make a new feature request for this.
Thanks for your feeback. :)
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
I wrote really similar debug class for my company.
It helps debug a lots. but, adding debug interface at the end of document breaks design too much such as iframe-ed pages or popup-ed pages. and debugging is hard on pages which is redirecting.
so, I changed my debug class by writing every log data on /tmp and it dosen't require calling function like writeDebug(). it uses exit_handler
.
so, whenever programmers need to debug, they can simply press shortcut button on their debug pages.
Well it could be achieved. I think to a new function , debugLog() , which would be called at the place of DebugDisplay or/and a new attribute could define the type of the output. For the Pear version, i will use Pear::Log of course.
It is not the first someone ask me to have the possibility to save debug as logs, so i think it will be a part of the next version. I will make a new feature request for this.
Thanks for your feeback. :)
For the new version V2, there will be a specific Log renderer for this purpose.