Nice!
I'm just looping panels right now with isinstance() to discern the correct
one.
It took a while to get the config right, but I was able to implement this
without any edits to debugtoolbar yet.
https://github.com/jvanasco/pyramid_debugtoolbar_api_sqla
--
You received this message becaus
I started to lay the groundwork for this in
https://github.com/Pylons/pyramid_debugtoolbar/pull/182 by making the
panel name a unique identifier that can be used in more places. This
work probably needs to be completed but I did it on that panel
activation branch which has some real problems waitin
I had an idea a while back for a Toolbar <-> Panel api, and I think I need
to build it out. hoping someone here can set me straight and offer some
better ideas on how to pull this off.
The simple idea:
1. Give each panel a `toolbar` attribute after instantiation. this
would allow any pan
