Re: Template Proposal

On Fri, 9 Nov 2001 13:51:09 -0500 "Dietrich Ayala" <dietrich@ganx4.com> wrote: > +1 > > The rigidity of the coding style is definitely turning some people away from > PEAR; people who *want* to contribute and be a part of it. Standarts do not mean rigidity, but viability. I really do not care about space or tabs, nl before brackets or not. The rules concern code re-use too, I will never use an "api" where every parts use his own string manager, errors managers or whatever you want. The questions to when someone will make his lib a part of PEAR will be more the need of this libs and how to rewrite part of this libs to use "lower levels api" or "fundations". Ooops :) here is a good point ;) another hotscripts, a fundation, a standart api ? ;). Maybe split PEAR in a standart api AND a repositary. > There is even less of an incentive to convert my code when: Community, when a new module has been "accepted" in PEAR, let us help you to convert/adapt your code. > 1. there is doubt that one's code will be accepted if there is similar > functioning code in PEAR already. IMO no doubt. If the functionnality is faster, more efficient and use same methods/properties replace the implementation, elsewhere where is the intererest ? > 2. new classes aren't getting distributed w/ PHP, and PEAR installer stuff > seems far from being usable by everyday PHP users (please correct me if i'm > wrong here. status on the state of the installer and a brief explanation of > how it works would be awesome, if anyone involved has the time). If there is something available, I should translate to french. btw which format do you use to submit new docs ? hth pa