paulj1999
asked on
Opinion Needed: Templating Engines vs XML / XSL Output
Hi,
I'm interested in getting some suggestions. Right now I'm developing an architecture which does the presentation layer using templeting. Now, my question / advice needed: Right now I'm doing XML / XSL translation. Part of the reason is I like the speed of using PHP's built in DOM framework, plus the output doesn't have to be HTML, I can output to whatever format I want. However, I'm thinking of using Smarty due to its ease of use and mostly because my architecture is for the Web. The only thing stopping me is I've heard (never fully investigated) Smarty is slow.
My questions: Do I stay w/ XML / XSL, move onto Smarty, or try another templeting engine. Please give some opinons, I would really appreciate.
I'm interested in getting some suggestions. Right now I'm developing an architecture which does the presentation layer using templeting. Now, my question / advice needed: Right now I'm doing XML / XSL translation. Part of the reason is I like the speed of using PHP's built in DOM framework, plus the output doesn't have to be HTML, I can output to whatever format I want. However, I'm thinking of using Smarty due to its ease of use and mostly because my architecture is for the Web. The only thing stopping me is I've heard (never fully investigated) Smarty is slow.
My questions: Do I stay w/ XML / XSL, move onto Smarty, or try another templeting engine. Please give some opinons, I would really appreciate.
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
XML+XSL will run only on browsers that support them. Nowadays browsers support them but if you plan to output for palmtops, mobiles etc my vote is towards templates.
Another advantage of templates is that they give you the freedom to create code for forming the layout. Plain XML only outputs information and sometimes this is not enough.
Another advantage of templates is that they give you the freedom to create code for forming the layout. Plain XML only outputs information and sometimes this is not enough.
I would implement a solution like this article talks about. Most template engines add a lot of overhead for little benefit.
http://www.massassi.com/php/articles/template_engines/
http://www.massassi.com/php/articles/template_engines/
Testiomonial:
http://www.phpinsider.com/smarty-forum/viewtopic.php?p=40905
If you ask me: things that make page slow are frames and too many (and) big pictures...
So if you use a CSS powered template wisely it should be pretty fast.
But as always - you will need to try it and see it for yourself.
Greets
Ljubiccica