Discussion:
Updates to Zend_Wildfire (Firebug/FirePHP logger)
Christoph Dorn
2009-01-14 02:33:33 UTC
Permalink
I have made some important updates to Zend_Wildfire. Code is in the SVN
trunk.


When logging objects in frameworks like ZF there can be many object
members that while important to the framework are of less interest when
debugging. If these members are logged they bloat the log message that
is sent to the client, they will slow down the client UI and make it
harder to inspect the members you actually want to see.

You can now exclude specific object members by class name and member
name with:

$firephp = Zend_Wildfire_Plugin_FirePhp::getInstance();
$firephp->setObjectFilter('Class_Name',array('Member1','Member2'));


When logging objects and arrays you can now limit the depth with:

$firephp->setOption('maxObjectDepth',3);
$firephp->setOption('maxArrayDepth',3);


You can also limit the number of steps in traces with:

$firephp->setOption('maxTraceDepth',3);


By default file and line information is now sent for each log message.
You can disable this with:

$firephp->setOption('includeLineNumbers',false);


Let me know what you think!
--
Christoph Dorn
<http://www.ChristophDorn.com/> http://www.ChristophDorn.com/
Bart McLeod
2009-01-14 09:29:03 UTC
Permalink
What I think is that you should do more promotion about firePHP offering
ZF integration: I did regular firePHP and even put the libraries on the
server, while I now understand they are actually in the framework (? or
are the libraries still needed, will have to read more docs :-) where
do I find the time).

Keep up the good work!

Bart
Post by Christoph Dorn
I have made some important updates to Zend_Wildfire. Code is in the
SVN trunk.
When logging objects in frameworks like ZF there can be many object
members that while important to the framework are of less interest
when debugging. If these members are logged they bloat the log message
that is sent to the client, they will slow down the client UI and make
it harder to inspect the members you actually want to see.
You can now exclude specific object members by class name and member
$firephp = Zend_Wildfire_Plugin_FirePhp::getInstance();
$firephp->setObjectFilter('Class_Name',array('Member1','Member2'));
$firephp->setOption('maxObjectDepth',3);
$firephp->setOption('maxArrayDepth',3);
$firephp->setOption('maxTraceDepth',3);
By default file and line information is now sent for each log message.
$firephp->setOption('includeLineNumbers',false);
Let me know what you think!
--
Christoph Dorn
<http://www.ChristophDorn.com/> http://www.ChristophDorn.com/
--
Bart McLeod
*Space Web Internet Team*
Middenlaan 47
6865 VN Heveadorp
The Netherlands
*t* +31(0)26 3392952
*m* 06 51 51 89 71
*@* info-***@public.gmane.org <mailto:info-***@public.gmane.org>
www.spaceweb.nl <http://www.spaceweb.nl> zce logo zce PHP 5 logo

/Bart McLeod is a Zend Certified Engineer./

Click to verify! <http://www.zend.com/zce.php?c=ZEND004591&r=218204904>
Christoph Dorn
2009-01-14 14:00:24 UTC
Permalink
ZF has had native FirePHP support since 1.6

See:
http://www.christophdorn.com/Blog/2008/09/02/firephp-and-zend-framework-16/

Christoph
Post by Bart McLeod
What I think is that you should do more promotion about firePHP
offering ZF integration: I did regular firePHP and even put the
libraries on the server, while I now understand they are actually in
the framework (? or are the libraries still needed, will have to read
more docs :-) where do I find the time).
Keep up the good work!
Bart
Loading...