Re: HTML_Template_IT cooperation status, competitive package proposal

Lukas Smith wrote:

Then I don't see the problem. Are we now only talking about adding or not adding caching?

In case you already forgot, the problem is as follows:

I once again propose my work as a separate package. I think it is in accordance with PEAR's policy on competitive packages (http://pear.php.net/manual/en/faq.competetive-packages.php): -------------- A good reason for a new class is often, that you are missing a function, behaviour or speed in an existing implementation. In this case, you should take a look at this class, if it possible to extend this class. If not, then you have a good reason to commit a new class. -------------- This is true: I'm missing some features in existing class and cannot extend it because the maintainer is against it. -------------- If you write a new class, try to keep API compatibility with existing classes as far as possible! -------------- The API of a new class is essentially the same as that of HTML_Template_IT. Their common behaviuor is the same, too. This can be checked by using unit tests that are now included with HTML_Template_IT.