Smarty

[marccho]

[Gerald]

[marccho]

[BRDude]

marccho, Microsoft satanism aside, "framework" is what I used to describe the set of features Smarty provides out-of-the-box. It's very refreshing when you can get them all up and ready to deploy by just doing an include('Smarty.class.php') and $template = new Smarty().

Regarding your alegations of colossal waste of cpu cycles with Smarty, this engine sets itself apart from others exactly for its efficiency through its ability to pre-compile templates, cache them and provide very fine-grained control over cacheability (geez, what else can you ask for?). It's what makes Smarty so much faster, just look at the actual benchmarks.

[marccho]

[BRDude]

This is going nowhere. I'm being humble and understanding, yet you accuse me of not understanding basic concepts, which is offensive. No hard feelings, let's just agree to disagree.

[marccho]

[boots]

Marccho enjoys talking to himself. Marccho has no new or intelligent ideas to share. Marccho has no legitimate business here.

The next person who claims that PHP is itself a templating language should do so with the understanding that they are harking back to the days of PHP2 and 3 when that was true. Then, the idea was that you'd encapsulate your business logic in C modules which would feed PHP's processing. That provided separation of two types of unrelated logics -- logic and processing. Some still do that, but the VAST majority of PHP coding doesn't work like that these days, many applications being written entirely in PHP. To regain the same separation, these aspects of design need to be reconsidered and Smarty provides one avenue to address that need. Sure, boring 10 line scripts hardly need Smarty, but sophisticated, maintainable and large applications often do require the types of features that Smarty brings to bare.

Marccho, stop spouting at the mouth and try to understand the tools at hand a bit better. Make sure you know you programming languages and techniques as well as you claim to know natural languages. One more thing--you DO have to read to understand and participate in discussions. Asserting that you don't like to hear that argument only underlines your disrespect for those of us who have spent considerable time analyzing and working with these issues.

[marccho]

Nothing to quote.

Wow, you are great man, if I just wanted I wouln't had been able to say something more stupid.

You are the boss. I agree with everything you may say, until my ears bleed.
_________________
Templating, like object oriented programming is not a piece of software.

[adamastor]

Well, I'm afraid I have to agree with marccho.

I'm using PostNuke and downloaded a module called Xanthia Templating Environment. This module replaces the default "display" logic of PostNuke with Smarty.

Before installing this module, my homepage (in a testserver) took 0,9s to load.

With Smarty the homepage now takes 2,1s. Exact Same content! Try It! Just folow those links.

This is not just some nanoseconds, and is just one simple request! Now, I've never used Smarty, and maybe I'm doing something wrong, so I would like to invite you to find the problem.

I was considering Smarty, but with these "nanoseconds" no thanks!

[MrSlayers]

Hi !
I write my text in French because the author understand French

Bon meme si je ne comprend pas tout l'anglais j'ai l'impression que ce topic est du "troll".
Je suis nouveau dans l'utilisation de Smarty mais je dois dire que j'aime smarty !! Avec Smarty je divise le temps de chargement de mes page par 8 !!

Passer de 150 ms à 18 ms pour les pages ce n'est pas rien !! (bien sur il faut utiliser le cache) .

Apres pour ce qui est de la charge CPU, forcement ca doit utiliser plus (perso j'ai pas encore vu de différence) mais il y a surement moyen d'optimiser ses pages .

[devnul]

This point that you are missing (and I am surprised nobody has specifically made it):

Smarty parses the template and creates a PHP-scripted HTML page. From then on, the PHP-scripted page is used just as if you had sat down and wrote it yourself. When the template is updated, it gets parsed one (and only) one time to create the PHP code.

All of that being said, I've been using Smarty for some time now and can definitely say that it has *radically* improved my productivity.

To consider Smarty a templating system is not really accurate - as pointed out by someone else it is actually more of a development framework. I'm surprised you can't see this - have you read the documentation or downloaded/installed it?


As a final point, considering something like this:

[devnul]

Whoops someone did make my point.. Sorry, I didn't make it to the second page when I posted that...

As for PostNuke: I would suspect that this has very little to do with Smarty itself. It is probably the way the module was written (either that or you do not have Smarty configured correctly). I've not developed any Smarty templated page which has taken longer then .25 seconds to render - and most of that is usually in database accesses/etc which would need to be done if Smarty were being used or not.

Greg Saylor
Senior Systems Integrator

[mikeken]

Just to put my 2 cents in on this. Marccho, please grow up. Why are you so mad because of something that you are not even forced to use? So immature.

Anyways, dont know if this point was posted yet but, suppose this scenario.
Php programmer with no designing skills what so ever. Really good designer with no php skills...get the pictures?

--Mike.

[markwest]