Re: Template ? focus on PHP5
| From: | Jan Lehnardt | Date: | Thu, 08 Jul 2004 09:20:37 +0000 |
| Subject: | Re: Template ? focus on PHP5 | ||
| References: | 1 2 3 | Groups: | php.pear.dev |
| Request: | Send a blank email to pear-dev+get-31740@lists.php.net to get a copy of this message | ||
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
Hi,
I'm just throwing in what came to my mind, when
reading this thread.
On 6 Jul 2004, at 8:58, David Costa wrote:
On Jul 5, 2004, at 2:43 AM, Alan Knowles wrote:Considering most users do have a PHP 4 template engine in place, that might work with 5 (not E_STRICT of course). On the advent of switching to PHP 5, would they consider moving to PEAR's uber-template class? Regardless of how superior technically it would be, they'd rather try (if available) a PHP 5 version of their existing engine, I think. The same for developers who are familiar and comfortable with one type of template class. New users, obviously, when evaluating which template engine to use now ("now" as in the transition time from PHP 4 to 5), would not go with a PHP 5 only package, when their hosters will run PHP 4 for another couple of months, maybe a year or even more. So the question here is, does the new template class have to worry about PHP 4 -> 5 transitions? Personally, I don't think so, because, as Alan states, it will take it's time to get the class stable, but even if it were ready by now, it is unlikely that the majority of Savant and FLexy and Smarty users simply switch over. And I do think the number of new users is negligible here; especially when talking about PHP 4 (which is the status quo) and the bunch of template systems we have, the number of new users will be spread over the template engines. Bye, Jan - -- GPG Key: BB96 56B0 Q: Thank Jan? - A: http://geschenke.an.dasmoped.net/ -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.2.3 (Darwin) iD8DBQFA7RHl7KW8t7uWVrARAlAhAKDMXBoKoz0DC21OKp+6A9rUQlWa9wCfXE4K xH45/4gbEw/4UiDm3/X+rGI= =R53E -----END PGP SIGNATURE-----I was hacking away at the Compiler backend for Template the other day, and it became clear that there is alot more work in refactoring the Flexy code (let alone looking at the Block Backend) Considering this may take many months before it delivers anything more than what Savant currently is, what are your thoughts on making Template a PHP5 only package?.I think is a great idea. I tried (as an experiment) to port Savant to PHP 5 E_STRICT and It was not as complex at all. I am all for a PHP 5 only template and many users will certainly benefit from it. Beside, I think that smarty and other template engines will be ported very late to PHP 5 (if anytime) so it would certainly be something new.