ANY INTEREST? Expansion of the sourceforge debugobject to support firePHP

[John Schlick]

I run the sourceforge debugObject project, and would like to know if there is any interest on the part of firePHP developers or users for having it support firePHP as an output mechanism.

FirePHP appears to be primarily an output mechanism for debug output, and the Debug_Object is more a way to control what debug output you see (with easy hooks for specifying it's output method)  it supports multiple levels of debug output and multiple scopes (routine, file, class, namespace, directory, everything, or any combination of the above that might make sense.)  If this were done the debug_object would effectively "wrap" firePHP for the users.

The project is hosted at https://sourceforge.net/projects/debugobject/ and the wiki contains good documentation.  Please take a peek and let me know if it seems appropriate.like extending it would be "worthwhile".  I should get replies to this post, but I am also available at John_S...@hotmail.com

[Christoph Dorn]

Do you have more info about debugObject than what is on the source-forge website? I did not find much in terms of docs.

Feel free to add support for FirePHP.

Christoph

[Christoph Dorn]

John Schlick

12 October, 2012 11:23 AM

In terms of docs... did you read the "instrumenting the code" and "turning it on" pages of the wiki?  If so, then please tell me what is lacking.  If not, then what did you look at that you thought were the docs? (and I really want to know since it's clear that if you didn't find the two critical pages of documentation, then I somehow need to make them WAY more prominent, and I haven't gotten much feedback in this area.)

Ah, I see them now. The links for the wiki did not display on sourceforge for some reason when I first checked (I also tried browsing SVN code and request timed out ... you may want to consider relocating your project to github.com).

As far as adding support for firePHP, feeling free to add support doesn't tell me that there are users out there that will want to use it.  I was hoping to get a number of people looking at it and saying "yes, I'd use it if it had firePHP support".  Is there a good way to get a sense that some portion of your community might be interested? (or might NOT be interested as the case may be.)

No, not really.

Existing FirePHP users are using FirePHP directly or via an existing logger with FirePHP support. I think it is unlikely for someone to switch to your library (if it had FirePHP support) without your library being popular first.

Christoph