HTML_Template_IT cooperation status, competitive package proposal
| From: | Alexey Borzov | Date: | Fri, 14 Mar 2003 10:53:44 +0000 |
| Subject: | HTML_Template_IT cooperation status, competitive package proposal | ||
| Groups: | php.pear.dev | ||
| Request: | Send a blank email to pear-dev+get-14285@lists.php.net to get a copy of this message | ||
Greetings!
Well, thanks to Lukas Smith's intervention some cooperation between
Pierre-Alain Joye and myself started. I created a bugfixing patch for IT 1.0
that was applied by Pierre. The unit tests that I made were also included in
the package. And that's where cooperation essentially ended.
Pierre's position:
All the new functionality except for 'cache' should be provided to him in form
of patches. Caching feature will never become a part of HTML_Template_IT.
My Position:
All new functionality including 'cache' should go in (an add-on class with it
is OK with me). I should have possibility to work on next major version of
HTML_Template_IT myself.
I already gave arguments for inclusion of 'cache' feature (that is somewhat
mis-named) both in pear-dev and in private to Lukas Smith and Pierre-Alain
Joye. If there is a need to repeat them, I'll do that.
Well, as no one is going to change his position anytime soon and as there are
some personal disagreements that you could observe in this list, 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.
The package is avaliable for download and review:
http://158.250.10.119/pear/IT%5bX%5d-fork.tar.gz
http://158.250.10.119/pear/IT.phps
http://158.250.10.119/pear/ITX.phps
As the package was essentially accepted to PEAR before Lukas Smith stepped in
to try to mediate (thanks again to him!), the only thing that prevents me
from releasing it is lack of suitable name. I propose HTML_Template_ReIT,
where "Re" stands for ReWrite, ReFactoring and possible future ReIntegration.
"IT" obviously stands for Integrated Templates.
Please vote for this proposal (I remember receiving a +1 for it already). If
you are against the name, please propose a better one.
Please do *not* restart the flames and/or try to convince Pierre or me in the
benefits of cooperation, everything will come in its time. And this
particular time has yet to come. :]