Comments on: PHP as a template language http://www.jansch.nl/2010/02/11/php-as-a-template-language/ Ivo's blog about PHP, the internet and life in general Wed, 08 Sep 2010 18:11:07 +0000 hourly 1 http://wordpress.org/?v=3.0.1 By: Faltzer http://www.jansch.nl/2010/02/11/php-as-a-template-language/comment-page-1/#comment-1088881 Faltzer Fri, 30 Jul 2010 17:51:03 +0000 http://www.jansch.nl/?p=2441#comment-1088881 Smarty is terrible; any templating engine that effectively evaluates PHP code is bad anyway. Hence why SUIT is better suited for the purpose of templating, because there is true separation of logic involved, and far less chance of security being compromised should an attacker gain access to your templates. Smarty is terrible; any templating engine that effectively evaluates PHP code is bad anyway. Hence why SUIT is better suited for the purpose of templating, because there is true separation of logic involved, and far less chance of security being compromised should an attacker gain access to your templates.

]]> By: Fedor http://www.jansch.nl/2010/02/11/php-as-a-template-language/comment-page-1/#comment-1046471 Fedor Sun, 11 Apr 2010 16:27:34 +0000 http://www.jansch.nl/?p=2441#comment-1046471 Smarty sucks!!! So much code for so little. Smarty sucks!!! So much code for so little.

]]> By: Ivo Jansch’s Blog: PHP as a template language | Development Blog With Code Updates : Developercast.com http://www.jansch.nl/2010/02/11/php-as-a-template-language/comment-page-1/#comment-1016481 Ivo Jansch’s Blog: PHP as a template language | Development Blog With Code Updates : Developercast.com Mon, 15 Feb 2010 19:08:02 +0000 http://www.jansch.nl/?p=2441#comment-1016481 [...] to his blog talking about one of the great debates in the world of PHP - is the language by itself a good templating language (versus using something like Smarty)? I think I’ve said it before. The tool you use should [...] [...] to his blog talking about one of the great debates in the world of PHP – is the language by itself a good templating language (versus using something like Smarty)? I think I’ve said it before. The tool you use should [...]

]]> By: Ivo Jansch’s Blog: PHP as a template language | Webs Developer http://www.jansch.nl/2010/02/11/php-as-a-template-language/comment-page-1/#comment-1016421 Ivo Jansch’s Blog: PHP as a template language | Webs Developer Mon, 15 Feb 2010 15:01:27 +0000 http://www.jansch.nl/?p=2441#comment-1016421 [...] to his blog talking about one of the great debates in the world of PHP - is the language by itself a good templating language (versus using something like Smarty)? I think I’ve said it before. The tool you use should [...] [...] to his blog talking about one of the great debates in the world of PHP – is the language by itself a good templating language (versus using something like Smarty)? I think I’ve said it before. The tool you use should [...]

]]> By: Hirvine http://www.jansch.nl/2010/02/11/php-as-a-template-language/comment-page-1/#comment-1016401 Hirvine Mon, 15 Feb 2010 14:57:17 +0000 http://www.jansch.nl/?p=2441#comment-1016401 ah form removed my php tags completely, but you get the idea I think :) ah form removed my php tags completely, but you get the idea I think :)

]]> By: Hirvine http://www.jansch.nl/2010/02/11/php-as-a-template-language/comment-page-1/#comment-1016391 Hirvine Mon, 15 Feb 2010 14:55:19 +0000 http://www.jansch.nl/?p=2441#comment-1016391 True, about messed up PHP, but your example actually shows a poor controller. A controller shouldn't use the same view for an error and valid xml. On the other hand, if I don't retain the `error` message idea, you may tell blank error message is no error. Which would preserve a single view. Short-tags is indeed irritating here. Mine would look like. Valid <result processed="processed? 'yes':'no'; ?>" <orderId="orderid; ?>" /> Error <result processed="processed? 'yes':'no'; ?>" <orderId="orderid; ?>" /> <error message="error; ?>" /> It also fixes your missing '<' in front of the order id element. You have also missed the self closing slash on order id element. Clearly Smarty didn't helped you to find those format errors. So no "Easy to Use and Maintain" story for Smarty. Hey don't get me wrong. It is what @Manes tells. Using smarty is depended by situation and business. Among friends PHP would do the trick, among a big business which uses different frameworks/cms you may think using template systems. True, about messed up PHP, but your example actually shows a poor controller.
A controller shouldn’t use the same view for an error and valid xml.
On the other hand, if I don’t retain the `error` message idea, you may tell blank error message is no error. Which would preserve a single view. Short-tags is indeed irritating here. Mine would look like.

Valid

<result processed=”processed? ‘yes’:'no’; ?>”
<orderId=”orderid; ?>” />

Error

<result processed=”processed? ‘yes’:'no’; ?>”
<orderId=”orderid; ?>” />
<error message=”error; ?>” />

It also fixes your missing ‘<’ in front of the order id element.
You have also missed the self closing slash on order id element.

Clearly Smarty didn’t helped you to find those format errors. So no “Easy to Use and Maintain” story for Smarty.

Hey don’t get me wrong. It is what @Manes tells. Using smarty is depended by situation and business. Among friends PHP would do the trick, among a big business which uses different frameworks/cms you may think using template systems.

]]> By: PHP as a template language « Aljo Guts http://www.jansch.nl/2010/02/11/php-as-a-template-language/comment-page-1/#comment-1016371 PHP as a template language « Aljo Guts Mon, 15 Feb 2010 14:40:11 +0000 http://www.jansch.nl/?p=2441#comment-1016371 [...] Latest news) One of the great debates in the world of PHP – is the language by itself a good templating language (versus using something like Smarty)? I think I’ve said it before. The tool you use should [...] [...] Latest news) One of the great debates in the world of PHP – is the language by itself a good templating language (versus using something like Smarty)? I think I’ve said it before. The tool you use should [...]

]]> By: 網站製作學習誌 » [Web] 連結分享 http://www.jansch.nl/2010/02/11/php-as-a-template-language/comment-page-1/#comment-1015411 網站製作學習誌 » [Web] 連結分享 Sat, 13 Feb 2010 14:16:42 +0000 http://www.jansch.nl/?p=2441#comment-1015411 [...] PHP as a template language [...] [...] PHP as a template language [...]

]]> By: Manes http://www.jansch.nl/2010/02/11/php-as-a-template-language/comment-page-1/#comment-1015391 Manes Sat, 13 Feb 2010 12:24:41 +0000 http://www.jansch.nl/?p=2441#comment-1015391 I agree with the point that the adoption of a technology depends on the business requirements: if you think Smarty is the right tool for the job when why not use it? Nevertheless, I don't see why a developer shouldn't look at the disadvantages of using such tool. I have never come across a website about any piece of software that lists its disadvantages and I am not surprised. I mean, why would you want to list the disadvantages of the product you've been working on? You don't need a degree in marketing to answer this question. Perhaps some really frustrated developer took the trouble to create nosmarty.net, maybe when he chose Smarty as the templating engine to use in production he had only looked at the advantages of it, whereas back then he needed to look at the bigger picture and maybe today he would have been a lot happier had he not chosen Smarty. I have used Smarty in the past and I personally think it's not bad, it did the job back then, but I wouldn't use it again today, I'm looking at alternatives such as PHPTAL: the logic is tightly integrated with the markup thus forcing you to write clean XHTML. Isn't that better? Plus, I saw Smarty code producing JavaScript code, XML feeds, documents later converted into PDFs. I know I am repeating myself, but when we all say we should use the right tool for the job, then why use Smarty to produce JavaScript code, XML feeds, documents? Any JavaScript library (Prototype, jQuery, etc.), the DOM extension and the PDF extension all seem to be better tools for the aforementioned examples. This is my humble opinion, feel free to disagree. I agree with the point that the adoption of a technology depends on the business requirements: if you think Smarty is the right tool for the job when why not use it?
Nevertheless, I don’t see why a developer shouldn’t look at the disadvantages of using such tool. I have never come across a website about any piece of software that lists its disadvantages and I am not surprised. I mean, why would you want to list the disadvantages of the product you’ve been working on? You don’t need a degree in marketing to answer this question.
Perhaps some really frustrated developer took the trouble to create nosmarty.net, maybe when he chose Smarty as the templating engine to use in production he had only looked at the advantages of it, whereas back then he needed to look at the bigger picture and maybe today he would have been a lot happier had he not chosen Smarty.
I have used Smarty in the past and I personally think it’s not bad, it did the job back then, but I wouldn’t use it again today, I’m looking at alternatives such as PHPTAL: the logic is tightly integrated with the markup thus forcing you to write clean XHTML. Isn’t that better? Plus, I saw Smarty code producing JavaScript code, XML feeds, documents later converted into PDFs. I know I am repeating myself, but when we all say we should use the right tool for the job, then why use Smarty to produce JavaScript code, XML feeds, documents? Any JavaScript library (Prototype, jQuery, etc.), the DOM extension and the PDF extension all seem to be better tools for the aforementioned examples.
This is my humble opinion, feel free to disagree.

]]> By: Sugar Developer Blog » Blog Archive » Smarty or PHP as a templating language? http://www.jansch.nl/2010/02/11/php-as-a-template-language/comment-page-1/#comment-1015221 Sugar Developer Blog » Blog Archive » Smarty or PHP as a templating language? Fri, 12 Feb 2010 20:49:03 +0000 http://www.jansch.nl/?p=2441#comment-1015221 [...] came across an interesting post by Ibuildings CTO Ivo Jansch, talking about the use of Smarty as a templating language over PHP [...] [...] came across an interesting post by Ibuildings CTO Ivo Jansch, talking about the use of Smarty as a templating language over PHP [...]

]]>