<?xml version="1.0" encoding="UTF-8"?><rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:dc="http://purl.org/dc/elements/1.1/"
	xmlns:atom="http://www.w3.org/2005/Atom"
	xmlns:sy="http://purl.org/rss/1.0/modules/syndication/"
		>
<channel>
	<title>Comments on: Top 5 php template engines</title>
	<atom:link href="http://www.rawseo.com/news/2009/04/06/top-5-php-template-engines/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.rawseo.com/news/2009/04/06/top-5-php-template-engines/</link>
	<description>A blend of programming and seo</description>
	<lastBuildDate>Tue, 23 Mar 2010 05:55:58 -0400</lastBuildDate>
	
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
		<item>
		<title>By: Justin (rawseo)</title>
		<link>http://www.rawseo.com/news/2009/04/06/top-5-php-template-engines/comment-page-1/#comment-3966</link>
		<dc:creator>Justin (rawseo)</dc:creator>
		<pubDate>Thu, 13 Aug 2009 13:48:09 +0000</pubDate>
		<guid isPermaLink="false">http://www.rawseo.com/news/?p=562#comment-3966</guid>
		<description>I&#039;ve never tried uberCart.  I will have to check it out.</description>
		<content:encoded><![CDATA[<p>I&#8217;ve never tried uberCart.  I will have to check it out.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: James</title>
		<link>http://www.rawseo.com/news/2009/04/06/top-5-php-template-engines/comment-page-1/#comment-3953</link>
		<dc:creator>James</dc:creator>
		<pubDate>Thu, 13 Aug 2009 03:23:47 +0000</pubDate>
		<guid isPermaLink="false">http://www.rawseo.com/news/?p=562#comment-3953</guid>
		<description>I just wanted to pitch in that I completely agree with the author&#039;s assessment of osCommerce.  I detest it as a platform and will do whatever I can to get customers off of it.  One solution I&#039;ve used effectively is UberCart with Drupal.  It&#039;s good for basic sites and anything I&#039;ve seen done in osCommerce can easily be done it UberCart.  And it separates the code from the design quite well.

Another technique I&#039;ve used to allow designers to work with the PHP backend is to set up PHP to parse HTML files and then the designer can design whatever they like and PHP statement just need to be created to dill in content.  I haven&#039;t worked out all the kinks for doing a large site this way though :)

James</description>
		<content:encoded><![CDATA[<p>I just wanted to pitch in that I completely agree with the author&#8217;s assessment of osCommerce.  I detest it as a platform and will do whatever I can to get customers off of it.  One solution I&#8217;ve used effectively is UberCart with Drupal.  It&#8217;s good for basic sites and anything I&#8217;ve seen done in osCommerce can easily be done it UberCart.  And it separates the code from the design quite well.</p>
<p>Another technique I&#8217;ve used to allow designers to work with the PHP backend is to set up PHP to parse HTML files and then the designer can design whatever they like and PHP statement just need to be created to dill in content.  I haven&#8217;t worked out all the kinks for doing a large site this way though <img src='http://www.rawseo.com/news/wp-includes/images/smilies/icon_smile.gif' alt=':)' class='wp-smiley' /> </p>
<p>James</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: kl</title>
		<link>http://www.rawseo.com/news/2009/04/06/top-5-php-template-engines/comment-page-1/#comment-1857</link>
		<dc:creator>kl</dc:creator>
		<pubDate>Mon, 25 May 2009 19:36:25 +0000</pubDate>
		<guid isPermaLink="false">http://www.rawseo.com/news/?p=562#comment-1857</guid>
		<description>This list needs PHPTAL. It&#039;s one of very few that protects against XSS and guarantees well-formed XHTML.</description>
		<content:encoded><![CDATA[<p>This list needs PHPTAL. It&#8217;s one of very few that protects against XSS and guarantees well-formed XHTML.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Zyx</title>
		<link>http://www.rawseo.com/news/2009/04/06/top-5-php-template-engines/comment-page-1/#comment-1057</link>
		<dc:creator>Zyx</dc:creator>
		<pubDate>Mon, 04 May 2009 10:07:07 +0000</pubDate>
		<guid isPermaLink="false">http://www.rawseo.com/news/?p=562#comment-1057</guid>
		<description>Yes, every MVC in PHP that follows this paradigm and puts view HTML code in a separate files **does** have a template engine. The definition suggested by you is a myth that has nothing to do with facts. Do you say that those views in the frameworks are executed by the higher powers and the script data self-assign to them without any help of any extra API? :) Let&#039;s follow your definition of a template engine and take a parser of external template language, for example from Smarty. To &quot;change&quot; such Zend_View into a template engine, you need approx. 10-30 lines of extra code: to check if the view has been modified and to run the external compiler. And what about Smarty 3? It will allow to write templates both in Smarty language and in pure PHP. How would you classify it? Half-template engine? How about Savant?

Of couse I do not say that Smarty is the best - in my opinion it is one of the worse template engines that shows, how **not** to make a template engine with an external language and the only advantage is that it is widely known. That&#039;s why I&#039;ve used it in my comparison. The general question of the discussion should be &quot;whether an external language in template engines is good or bad thing&quot;.</description>
		<content:encoded><![CDATA[<p>Yes, every MVC in PHP that follows this paradigm and puts view HTML code in a separate files **does** have a template engine. The definition suggested by you is a myth that has nothing to do with facts. Do you say that those views in the frameworks are executed by the higher powers and the script data self-assign to them without any help of any extra API? <img src='http://www.rawseo.com/news/wp-includes/images/smilies/icon_smile.gif' alt=':)' class='wp-smiley' />  Let&#8217;s follow your definition of a template engine and take a parser of external template language, for example from Smarty. To &#8220;change&#8221; such Zend_View into a template engine, you need approx. 10-30 lines of extra code: to check if the view has been modified and to run the external compiler. And what about Smarty 3? It will allow to write templates both in Smarty language and in pure PHP. How would you classify it? Half-template engine? How about Savant?</p>
<p>Of couse I do not say that Smarty is the best &#8211; in my opinion it is one of the worse template engines that shows, how **not** to make a template engine with an external language and the only advantage is that it is widely known. That&#8217;s why I&#8217;ve used it in my comparison. The general question of the discussion should be &#8220;whether an external language in template engines is good or bad thing&#8221;.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: cafeda'</title>
		<link>http://www.rawseo.com/news/2009/04/06/top-5-php-template-engines/comment-page-1/#comment-1030</link>
		<dc:creator>cafeda'</dc:creator>
		<pubDate>Sun, 03 May 2009 17:07:10 +0000</pubDate>
		<guid isPermaLink="false">http://www.rawseo.com/news/?p=562#comment-1030</guid>
		<description>http://thietkexinh.com/TxTemplate/
Easy to use!</description>
		<content:encoded><![CDATA[<p><a href="http://thietkexinh.com/TxTemplate/" rel="nofollow">http://thietkexinh.com/TxTemplate/</a><br />
Easy to use!</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Tim_Myth</title>
		<link>http://www.rawseo.com/news/2009/04/06/top-5-php-template-engines/comment-page-1/#comment-955</link>
		<dc:creator>Tim_Myth</dc:creator>
		<pubDate>Fri, 01 May 2009 16:13:42 +0000</pubDate>
		<guid isPermaLink="false">http://www.rawseo.com/news/?p=562#comment-955</guid>
		<description>I think the best strength of a templaing engine is that a developer can offer templating choices to users without giving them access to ANY logic. That additional layer of abstraction makes your server just a little more secure with very little additional effort on your part.</description>
		<content:encoded><![CDATA[<p>I think the best strength of a templaing engine is that a developer can offer templating choices to users without giving them access to ANY logic. That additional layer of abstraction makes your server just a little more secure with very little additional effort on your part.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Tony</title>
		<link>http://www.rawseo.com/news/2009/04/06/top-5-php-template-engines/comment-page-1/#comment-703</link>
		<dc:creator>Tony</dc:creator>
		<pubDate>Fri, 24 Apr 2009 18:50:55 +0000</pubDate>
		<guid isPermaLink="false">http://www.rawseo.com/news/?p=562#comment-703</guid>
		<description>Zyx: no, just putting your views in a separate directory doesn&#039;t make it a templating engine.  If this were the case, every MVC framework could be called a templating engine (and I definately don&#039;t see any MVC frameworks in this post).  The point is that you shouldn&#039;t have to learn and implement some other special templating language for your views.</description>
		<content:encoded><![CDATA[<p>Zyx: no, just putting your views in a separate directory doesn&#8217;t make it a templating engine.  If this were the case, every MVC framework could be called a templating engine (and I definately don&#8217;t see any MVC frameworks in this post).  The point is that you shouldn&#8217;t have to learn and implement some other special templating language for your views.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Zyx</title>
		<link>http://www.rawseo.com/news/2009/04/06/top-5-php-template-engines/comment-page-1/#comment-345</link>
		<dc:creator>Zyx</dc:creator>
		<pubDate>Fri, 10 Apr 2009 15:16:20 +0000</pubDate>
		<guid isPermaLink="false">http://www.rawseo.com/news/?p=562#comment-345</guid>
		<description>Tony -&gt; If you put your view files in a separate directory, you get nothing more, nothing less, but a template engine. It does not matter, whether the view files contain curly brackets or PHP statements, they are still templates and the layer that handles it is a template engine. And an enormous number of successful PHP applications uses some kind of template engine, even if it is not called &quot;template engine&quot;...</description>
		<content:encoded><![CDATA[<p>Tony -&gt; If you put your view files in a separate directory, you get nothing more, nothing less, but a template engine. It does not matter, whether the view files contain curly brackets or PHP statements, they are still templates and the layer that handles it is a template engine. And an enormous number of successful PHP applications uses some kind of template engine, even if it is not called &#8220;template engine&#8221;&#8230;</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: ??????? &#187; [Web] ????</title>
		<link>http://www.rawseo.com/news/2009/04/06/top-5-php-template-engines/comment-page-1/#comment-304</link>
		<dc:creator>??????? &#187; [Web] ????</dc:creator>
		<pubDate>Thu, 09 Apr 2009 02:55:56 +0000</pubDate>
		<guid isPermaLink="false">http://www.rawseo.com/news/?p=562#comment-304</guid>
		<description>[...] Top 5 php template engines [...]</description>
		<content:encoded><![CDATA[<p>[...] Top 5 php template engines [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: abcphp.com</title>
		<link>http://www.rawseo.com/news/2009/04/06/top-5-php-template-engines/comment-page-1/#comment-252</link>
		<dc:creator>abcphp.com</dc:creator>
		<pubDate>Tue, 07 Apr 2009 08:08:31 +0000</pubDate>
		<guid isPermaLink="false">http://www.rawseo.com/news/?p=562#comment-252</guid>
		<description>&lt;strong&gt;Top 5 php template engines &#124; A blend of programming and seo...&lt;/strong&gt;

Successful PHP applications and projects do not require a template engine. However, when a project starts to involve both programmers and designers, it is a good idea to separate application code from presentation. Another benefit of this model is with...</description>
		<content:encoded><![CDATA[<p><strong>Top 5 php template engines | A blend of programming and seo&#8230;</strong></p>
<p>Successful PHP applications and projects do not require a template engine. However, when a project starts to involve both programmers and designers, it is a good idea to separate application code from presentation. Another benefit of this model is with&#8230;</p>
]]></content:encoded>
	</item>
</channel>
</rss>
