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 waiting to be solved.
We would probably take that work and provide some sort of
find_panel(name) api which would possibly solve most of your
complaints.
On Tue, Dec 16, 2014 at 11:25 AM, Jonathan Vanasco
jonat...@findmeon.com wrote:
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 panel to loop through the toolbar's panels, and access the
information on another one.
2. add a config.scan in __init__.py for panels/
Why?
The toolbar panels generally work by stashing a lot of information on
the request object, this is a lot of great info -- but only accessible to
the panel itself. If panels could find one another (and a new view could be
added), it would be trivial to do things like creating an API endpoint that
can pull that data out.
This is my practical use-case example: The unit test that ensures all my
routes work also times the pages; a few pages have shown troubling times and
I need to inspect them. Just about all the information I need is in the
Performance and SqlAlchemy panels. It would be fairly simple to piggyback
on all the work done by the debugtoolbar team, and simply parse the pDebug
link from the response, then have a followup request pull the data from an
endpoint and save it to a text file.
--
You received this message because you are subscribed to the Google Groups
pylons-devel group.
To unsubscribe from this group and stop receiving emails from it, send an
email to pylons-devel+unsubscr...@googlegroups.com.
To post to this group, send email to pylons-devel@googlegroups.com.
Visit this group at http://groups.google.com/group/pylons-devel.
For more options, visit https://groups.google.com/d/optout.
--
You received this message because you are subscribed to the Google Groups
pylons-devel group.
To unsubscribe from this group and stop receiving emails from it, send an email
to pylons-devel+unsubscr...@googlegroups.com.
To post to this group, send email to pylons-devel@googlegroups.com.
Visit this group at http://groups.google.com/group/pylons-devel.
For more options, visit https://groups.google.com/d/optout.
