[TYPO3-ect] The chain

Elmar Hinz elmar.DOT.hinz at team.MINUS.red.DOT.net
Tue Jan 23 11:39:46 CET 2007


Am Tue, 23 Jan 2007 11:01:04 +0100 schrieb Martin Ficzel:

> i think a generalized interface for value printing is necessary. and i
> definitely belongs into a view baseclass. so the question is weather the
> existing function set is complete and correct.
> 

You are right that functions like asText, asHtml, etc. are useful for
different template engines. I will exeperiment with one of the smaller
template engines, to find out, how such an engine can be integrated and
how this common functions can assist here, either by inheritence or in
form of a helper class.

> additionally the render($view) method should be defined as
> abstract/empty method in the base class because it basically that is the
> only method all views have to implement.
> 

The name of the render function isn't of that central importance in
SPL. External rendering engines may have other names for it. We don't need
to be that strict here. Enough flexibility is given by the possibilty to
exchange the actions. So we can define specific actions for any rendering
engine that matches it's API.

>>> 2. why is there no implementation of the old ###MARKER### template style
>>> . i know that smarty and phpView have much more features but many
>>> template developers learned the classic scheme. maybe a notation like
>>> ####MERKER::ASXXX### can fill the gap.
>> 
>> I guess there is no implementation because you havn't implemented it yet,
>> as far as I know. Did you? ;-)
> 
> :-)) very good point ... i wanted to figure out weather youd did'nt want
> to see the old template style because of some design resons.
> 

lib/div is flexible enough to work with any template engine. There are no
limits. It will even work with the old template style. :-) 

You even could connect JAVA based rendering engines or othe languages.
Would be interesting to do printing with FOPs for example.

> i will think about how it could be done but before i can do anything i
> still have to dive deeper into the lib/div system. im still at the
> beginning.
> 

You are welcome.

Elmar



More information about the TYPO3-team-extension-coordination mailing list