RE: [PEAR-DEV] Re: [PEAR] Re: [PEAR-DEV] new template engine

> > > Which Advantages has Smarty opposite the Intergrated > > > Template IT[X] ? I am very satisfied with the IT[X], > > > the ITX is clear still very unstably but to this one > > > can work. The point is not so much the technical merits of SMARTY vs. IT[X], or at the least, it should not be. The point is that there are a lot of people who are using SMARTY (PHPLIB Templatess and so on) and these people would like to be able to use the templates they have always used but as PEAR components. The point here to consider is not so much whether one template engine is better than another, the point is that if PEAR were to include those components that people either like to use now, would like to use in the future, or perhaps most importantly, plan to use, they would obviously see PEAR as much more attractive. This could have the effect of making PEAR seem indispensible. The result, I argue would be: increased use of PEAR, increased awareness of PEAR, increased involvement with PEAR, increased contributions to PEAR and on and on... which I feel is a good thing. If you think about it, there are still people out there who insist UNIX is better than Linux, maybe so, but the bottom line is that Linux moved the *NIX world a giant leap forward, which in turn has had the ironic effect of making Unix more attractive than ever. If one template engine is truly superior to another, then in the end, that template engine will be just that, the superior template engine, because that is the one people will use, further develop, further document, etc etc etc. Who really cares what happens to the others? At most they eat up a few bits of disk space lingering around on the CVS server. I see the addition of SMARTY, PHPLIB Templates, CachedFastTemplate and others as a big move forward and as a real turning point in PEAR's development if we allow it to occur. Moving in such a direction would send a message that PEAR is ready to move forward and wants to open its doors to others for contributions. As it stands PEAR is facing a real crisis as there are a lot of people who are feeling dienfranchised and like the developers of PEAR are nothing but a bunch of snooty programmers doing their own thing with no sense of community. Of course I am not making that accusation but I have seen that attitude out there on the net. Anyway... not to sound too critical, or to start a flame war, but I really think it is obvious that people really want to have a shared code repository that accommodates their needs, even if it means there are a few extra files, or it adds a little confusion here and there. Also, for the most part I think there is a general consensus that most people would like this code repository to be PEAR and not some other forked project. At the moment, there are many template engines in use, but they all lack something somewhere, bring them into PEAR, and eventually one will shine above the others and it will benefit us all. again... my 2 cents. Alan