[TYPO3-ect] Your experiences with Smarty

[R. van Twisk]

Steffen Kamper wrote:
> "Elmar HInz" <elmar.hinz at team.MINUS.red.DOT.net> schrieb im Newsbeitrag 
> news:mailman.1.1173344042.2408.typo3-team-extension-coordination at lists.netfielders.de...
>   
>> Hello Ries, Steffen and others,
>>
>> meanwhile you have done some experiments with lib/div and Smarty. I didn't
>> work with it myself. I would like to find an answer to this question:
>>
>> Do we need a Smarty connector object (smartyView)?
>>
>> Maybe Smarty has an API itself that doesn't need a special connector
>> object. Maybe such an object could be of help.
>>
>> What is your experience? What is your vision?
>>
>> Regards
>>
>> Elmar
>>
>>
>>     
>
> Hi Elmar,
>
> Ries build up a gallery with lib/div and smarty and we discussed a lot.
> First we moved to rpt_smarty because it's the better ext, later update (but 
> still has to be updated)
>
>   
SInce I cannot publish this extension, I will be the time and after the 
gallery system is done
I'll make a simple extension, OR use one of the current extensions and 
add a smarty view
to it.
> Then smartyView is used as central point for
> - initializing smarty
> - assigning values
>   
It's currently not used for assigning data to it, so we use the 'normal' SPL
functions, and we assign all data to smarty in one call as suggested by 
Elmar.

> As you mentioned, there are several ways to use smarty, if smarty is 
> initialised, you can assign values from every place.
> But to keep the model of MVC clear and the methods transparent, i would say 
> yes.
>   
MVC is central and from teh model or controllers point of view there is 
no almost no difference.
The current difference is that init() needs to be called. But w can get 
rid of it by initialising
smarty in the render method rather then in the init method. Steffen, 
would this be ok to you?

> I will do some improvements too and will update the smartyView at WE.
>   
I'll send you my current smarty version....
> vg  Steffen 
>
>
>