[TYPO3-ect] new version of smartyView

[Elmar Hinz]

Simon Tuck wrote:

> Steffen Kamper wrote:
>> 
>> The dependency changed from smarty to rpt_smarty, which is the better and
>> newer extension
>> (i'm not happy that both extensions never updated and the authors don't
>> respond)
>> 
> 
> Hi Steffen,
> I'm the author of the rtp_smarty extension and have just started using
> the lib/div framework and come across the smartyView class. I apologize,
> I had no idea the extension was being used here. We have some time on
> our hands and I had planned to do some work on the extension over the
> next weeks (There are a few issues and also there is a newer smarty
> version).
> I wanted to know if there is any feedback on your side re. rtp_smarty,
> particularly with regards to the smartyView class. Also would it make
> sense for you if I published the extension to the typo3 ext svn
> repository? Thanks & regards,
> Simon


Hello,

I just want to give some hints to the future of lib/div views in general. I
guess you all agree, that it will be a nice target to get a common API for
all type of rendereres, so that we quickly can exchange them.

For this reason I plan to separate the formatting processor (asRTE, asDate,
asText, asHtml, etc.) from the template engine processor (Smarty, PHP,
T3, ...). Also link generation and image tags should probably be treated in
their own processors. 

Please have a look at the wiki page and the latest SVN versions of
bananas/lib for the concept of the action pipeline of processors.

http://wiki.typo3.org/index.php/Action_Pipeline
http://wiki.typo3.org/index.php/MVC_Framework/lib_div_Beta_Branch

The template engines will mainly need to fill the placeholders in future,
while formatting is controlled by TS and/or FF by other processors.
Rendering engines still have to handle the templates logic like checking
for empty list arrays.

Building rendering processors like the smarty processors will only be a few
line of code, so that we can ship a broad range of alternatives.

You can find different solutions to handle subtemplates. One possible answer
is the PAC thingy.

http://wiki.typo3.org/index.php/MVC_Framework#The_Tree_of_Plugins_.28TOP.29
http://t3flyers.wordpress.com/2007/08/06/the-presentation-abstraction-control-architecture-of-typo3/


Regards

Elmar