The Django Debug Un-Toolbar
October 13, 2008
Anyway, the more I thought about it, I figured it probably best to not manipulate the DOM at all. In some discussion with others, it was determined a very useful adaptation to the project would be to serialize off all the data collected in the middleware on the server and set a cookie to a special path so that it could be retrieved via something like a bookmarklet.
So that's what I did. I forked the Django Debug Toolbar project and renamed it to Django Debug Un-Toolbar, real original, I know. While I don't expect it to be perfect yet (I spent about 2 hours this evening making sweeping and hurried changes to the code base), it does work as intended.
There are a number of things I want to add/change before I dare think about using in production. Yes, I think it would be useful to have in production, and triggered to turn on in a number of different ways -- either through changing a settings parameter to passing it a special query string parameter, or working for certain users.
By having the debug "toolbar" work in this manner it will be possible to collect all this good debug information from customers who's screens are unavailable to see when things inevitable go wrong and you need to troubleshoot things quickly.
I am closing the Un-Toolbar fork in favor of the other fork that i created that is more upstream compatible. Hopefully that fork is only temporary as well as I'd hope to get it worthy of merging back to Rob's repository.