Michael Graham wrote:
Rhesa,
This is too cool! I can think of all sorts of uses for this. For
instance, it would be very useful to have a simple
logger/dumper/debugger plugin that lets you dump the app state at
various points in the app's life cycle.
I'm imagining a LogDispatch plugin that would collect those, and hand
them over to DevPopup at the right time. This would be a great aid in
development. I usually have a bunch of "tail -f"'s running, but this
would be much easier to inspect!
One of the problems that I often have is that the $self object is so big
that it's pretty pointless to dump it to the error log. But a
browseable version of the $self object using the DHTML-based folding
tricks that you use for reports would be very useful.
Absolutely
Regarding the timings plugin I have a couple of suggestions:
* the name of the current template is available to the load_tmpl hook -
it would be nice if this were displayed in the report (useful when
there are a a lot of templates filled in a single request)
I agree, and I actually thought of it, only after I had uploaded this
dist. It will help a lot though.
* the Timing module could register its own cgiapp hook - something like
'devpopup_timings'. Then the user could log the timing of critical
points in the app by calling (e.g.):
$self->call_hook('devpopup_timings', 'Before database call');
do_some_expensive_db_stuff();
$self->call_hook('devpopup_timings', 'After database call');
Excellent suggestion! I was already deploring the lack of an
after_prerun and such; the current list isn't exactly detailed. An extra
hook will be wonderful indeed! And that way I don't even have to export
anything, which is even better.
This will definitely be in 0.02 :)
Great work!
Thanks for the great reception!
Rhesa
---------------------------------------------------------------------
Web Archive: http://www.mail-archive.com/[email protected]/
http://marc.theaimsgroup.com/?l=cgiapp&r=1&w=2
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
