[Fwd: Re: [PEAR-DEV] Re: [ANNOUNCEMENT] HTML_CSS-1.0.0RC1 (beta) Released.]
| From: | Lukas Smith | Date: | Tue, 26 Jul 2005 21:06:13 +0000 |
| Subject: | [Fwd: Re: [PEAR-DEV] Re: [ANNOUNCEMENT] HTML_CSS-1.0.0RC1 (beta) Released.] | ||
| Groups: | php.pear.dev | ||
| Request: | Send a blank email to pear-dev+get-38944@lists.php.net to get a copy of this message | ||
just so that others can follow up on this as well.
-------- Original Message --------
Subject: Re: [PEAR-DEV] Re: [ANNOUNCEMENT] HTML_CSS-1.0.0RC1 (beta) Released.
Date: Tue, 26 Jul 2005 23:04:48 +0200
From: Laurent Laville <pear@laurent-laville.org>
To: Lukas Smith <lsmith@php.net>
References: <20050726165933.11282.qmail@pb12.pair.com> <42E6756D.3040705@php.net> <42E67BC7.3030602@capitalfocus.org> <42E69A53.2070303@laurent-laville.org> <42E69AFD.8060503@php.net> <42E6A0D0.4040801@laurent-laville.org> <42E6A1D8.7050907@php.net>
Lukas Smith wrote:
Laurent Laville wrote:Klaus and of course all others users about this such plug-in error system [2], [3], [4], [5] As my english is not always as good as i wanted, Klaus has fixed some minor syntax language for me ! regards Laurent [1] http://cvs.php.net/pear/HTML_CSS/docs/errorHandlerGuide.txt [2] http://cvs.php.net/co.php/pear/HTML_CSS/CSS.php?r=1.43#1386 [3] http://cvs.php.net/co.php/pear/HTML_CSS/CSS.php?r=1.43#1437 [4] http://cvs.php.net/co.php/pear/HTML_CSS/CSS.php?r=1.43#1468 [5] http://cvs.php.net/co.php/pear/HTML_CSS/CSS/Error.php?r=1.2I'm just a bit worry to see such discuss, long time after i've already implemented this solution. If you are against such coding, why tell it now , and waiting so long :-( I know that HTML_Progress is not a well-known package as HTML_CSS or many others could be.I havent followed the CVS commits closely until recently. Anyways could you point me to the necessary code parts I should be looking at to see what you have done. I am only worried that you are making things harder to use for PEAR users, just to please people that for usually questionable reasons believe they should not be using PEAR code. Please post your reply to pear-dev to give other people a chance to also take a look t your solution. Maybe it should become the standard solution or a recommended solution. regards, Lukas I suggest you to have a look on the documentation i've written [1] for