[TYPO3-ect] lib/div 1.0 - it's time to say thank you

[Steffen Kamper]

"Jochen Rieger" <j.rieger at connecta.ag> schrieb im Newsbeitrag 
news:mailman.1.1168340287.22754.typo3-team-extension-coordination at lists.netfielders.de...
> Hi all,
>
>> -1 for Smarty.
>
> I agree with Cyprian. What I mainly didn't like about SMARTY is that you 
> are tempted to put a lot of logic (even PHP functions) into the templates.

not in general :-) The easiest way of a smarty template is that you have 
markers like
{$name}
instead of the "normal" TYPO3-Marker
###NAME###

So you don't have to know something about the logic.

The good thing is, that you can implement some logic into:
{if $name=""} I don't find a name to this subjsct {/if}

which makes it easy instead of writing complicate stdWrap-Constructs with 
TS.

You also have the possibility to integrate language vars from the 
locallang.xml like
{getLL}archiveItems{/getLL}

In my opinion the syntax is easy. If there are some programmers want make 
more complex solutions, they can do, cause smarty is really powerful.

The second thing is that smarty can handle loops, so this part hasn't to be 
coded in extension, you only have to fill an array - next +1 :-)

At the end there will be several opinions the user can switch to:
- php template
- smarty template
- may be more coming ...

vg  Steffen

>I don't think that this belongs there. IMO it somehow is the opposite 
>direction of what should be achieved by concepts like MVC.
>
> So... 1- for Smarty as well.
>
> Of cause it's handy sometimes to just fiddle around in the templates and 
> adding functionality / conditions etc. there, but this is not in the sense 
> of MVC I think.
>
> Regards,
> Jochen