Re: New class - how to contribute ?

From: Date: Wed, 18 Sep 2002 16:34:34 +0000
Subject: Re: New class - how to contribute ?
References: 1  Groups: php.pear.dev 
Request: Send a blank email to pear-dev+get-9172@lists.php.net to get a copy of this message
On 2002-09-18 17:33, while getting another beer from the fridge I saw a little yellow card, on which Brent Cook wrote:
On Wed, 18 Sep 2002, [ISO-8859-2] Wojciech Zieli?ski wrote:
I think that a good first step would be to look at the I18N code in CVS (http://cvs.php.net/cvs.php/pear/I18N) and compare it to your localization class. The folks behind that class were looking for feedback too and, since you've had time to think about and use your class, you can help by suggesting changes and improvements to the PEAR class, or maybe propose yours as an alternate approach. Could you suggest some pros and cons between your class and the PEAR class? I think that the PEAR I18N code could use some testing and improvements, if the CVS comments are to be believed. - Brent
As far as I found out - this class demonstrates completelly another approach. This class is the template - while main is to give to the developer functions that will allow him to quickly and easily get the correct translation from the database. As for the pluses and minuese of both: I18N is much more complicated to learn, but gives to the user much more functionality. As I said - main is only for Translation - the I18N is also creating the HTML code. That's why I am afraid I will not be able to some kind of "merge" my class to the I18N - bacouse as I said they are completely different on the lowest level :) Or maybe the developers of I18N would see some chance ? However I still think, that my class does not duplicate the functionality of I18N. I18N will be used when developer wants to make the whole site using the temlate approach. When he wants only to translate the site (becouse e.g. he already has some template engine implemented) - it would be easier to use my class. Regards Voyteck

« previous php.pear.dev (#9172) next »