Re: Re: [ANNOUNCEMENT] HTML_CSS-1.0.0RC1 (beta) Released.
| From: | Laurent Laville | Date: | Tue, 26 Jul 2005 20:17:23 +0000 |
| Subject: | Re: Re: [ANNOUNCEMENT] HTML_CSS-1.0.0RC1 (beta) Released. | ||
| References: | 1 2 3 | Groups: | php.pear.dev php.pear.dev |
| Request: | Send a blank email to pear-dev+get-38925@lists.php.net to get a copy of this message | ||
Klaus Guenther wrote:
On 7/26/2005 7:39 PM, Lukas Smith spake the following words:I'll try to explains, as much clear as i can. First i've implemented this open error handling system on my html_progress2 package after many try. Someone remember perharps that i've tried to implement the PEAR_ErrorStack alone. And yeah, it was awesome. But i was not very happy with a such restrictive solution. PEAR_Error is good but with PEAR_ErrorStack, Greg show us the limit of PEAR_Error and the cool features of ErrorStack (context, dynamic message generation, ...). As i've in mind to produce a html_progress2 version without dependencies for no PEAR users, and those who don't want to install the PEAR framework, i realized that first step will be to have a error handler that support what Error system you might want. PEAR_Error by default, but also PEAR_ErrorStack and whatever you would plug-in. Of course some code/features, of html_css / html_progress2, error handler are part of PEAR_ErrorStack. I think it's the best of two worlds. And you may choose your own way / solution with few efforts. To resume: To know, why i wrote this such plug-in system on both progress2/css, you should anlyse the source code, and you 'll certainly have your answer. As Greg said: "Unfortunately, it appears to be too much effort for some developers." But if you take a little time, you'll learn a lot, as did it in past with PEAR_ErrorStack. Special thanks to Greg Beaver who opened a nice way ! LaurentPEAR Announce wrote:That was Laurent's work. Don't know exactly how it makes everything better except that it seems rather cool now that PEAR_ErrorStack is being split out into its own package. Laurent, could you expound on it? Klaus- PEAR_ErrorStack was replaced by a simple way to plug in any error handling system you might want (default used PEAR_Error object)could you elaborate on this? wasnt this the original purpose of ErrorStack?