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

[Cyprian Kowalczyk]

On Tue, 09 Jan 2007 14:15:01 +0100, Steffen Kamper <steffen at dislabs.de>  
wrote:

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

You can use whatever markers you like in Typo, even {$name}, no problem  
with that.

I'm using for instance something like:
###record::fieldName###
and then process such a calls in my plugins quasi-automatically.


> 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.

But is it a true MVC approach?
You are mixing View with Controller here.
I'm nat talking about usability of smarty approach but it consistency.
So why not to use:
<?= name ?>
<? if ($name) : ?>
something
<? :endif ?>

I can't see many differences between those two approaches in terms of  
syntax.
And the latter if native PHP, so way faster.

Besides you should do such a things in Controller part.

In my dream Typo3 teplate engine I would like to choose parts and then  
apply conditions for displaying them and so on.

-- 

regards, Cyprian
http://pi2.pl design project