This concern is precisely why we're promoting an 'extras' library in the
new proposal process:
http://framework.zend.com/wiki/display/ZFPROP/New+Proposal+Process+Detai
l+Draft. I haven't looked in to the value proposition here in any detail
myself, but it seems that many people in this forum find it at least
very intriguing. If someone is willing to put the effort in to put in a
proposal and meet our code and documentation quality guidelines, given a
critical mass of ZF developers seeing value here there is no reason we
shouldn't include it as part of the framework. But you're right- there
are lots of external dependencies, so maybe this isn't something that
Zend could support well. That's where 'extras' might come in.
And let me make this perfectly clear- we would fully expect that there
will be components in 'extras' that are more popular than those in the
standard library. We will also do everything we can to make sure extras
get as much exposure and are as adoptable as the components in the
standard library. The only significant difference is whether Zend can
support them with its paid support subscription; that's all.
So, I would say put together a proposal and don't worry about whether it
is a candidate for the standard library or not. If it ends up there then
great. If not, then great- it should share the same benefits that the ZF
project can bring to any PHP5 library.

Hope that helps.
,Wil

> -----Original Message-----
> From: Christoph Dorn [mailto:[EMAIL PROTECTED]
> Sent: Saturday, April 12, 2008 10:25 AM
> To: Thomas Fritz
> Cc: [email protected]
> Subject: Re: [fw-general] Zend_Log_Writer_FirePHP
> 
> > Perhaps it would be a nice addition for Zend_Debug::dump() too,....
> 
> 
> It would be great to add it to the Zend_Debug class. Ideally as a
> static
> method called fb() so that you can call Zend_Debug::fb() This way it
> stays isolated from Zend_Debug::dump() and can be optionally used.
> 
> I am just wondering if this use case is generic enough to be included
> in
> the Framework by default given that it only works with Firefox at the
> moment and the Firebug and FirePHP extensions must be installed.
> 
> Any guidance as to how we could integrated this would be great.
> 
> Christoph

Reply via email to