[TYPO3-dev] domesticating t3lib_div::debug

[Franz Holzinger]

Dmitry Dulepov [typo3] a écrit :
> Franz Holzinger wrote:
>> I think beko_debugster is better and I have
>> improved the code of cc_debug in a similar way.
> 
> I did not see that. Can you give a short intro?
> 
> I am only +1 to a good debugging api in core.

With cc_debug it sometimes happens that you do not have any debug popup
window. The reason can be an error in HTML, CSS or JavaScript on the
site. This is annoying. You must fix the bugs in the extensions before
you can do your debugging.

With beko_debugster you will always see the debug info. I have enhanced
this extension too.
And beko_debugster already gives you infos which code lines in which
files have been called before. This is very helpful to debug a function
which has been called from many other places. You can do a debug
backtrace. The drawback is that the output is put on the same page and
you have to scroll down. But you will always get the debug info.


- Franz