[TYPO3-50-general] New templating system?

[Simon Browning]

How about just porting TV over to v5 (+ maybe a light version for Duch :))

Seems to me its got lots of supporters (2nd most popular extension in 
the TER), its easy to use and works well.

Simon




On 23/03/2010 2:38 PM, "Duch (aka. Grégory Duchesnes)" wrote:
> for the sake of everyone, i'll try to summarize the talks and elaborate on a proposal.
>
> To the initial question "will there be a new templating system for Typo3 5" the answer seems to be "might be but Fluid is the best candidate".
>
> The debate has raised a series of other questions :
>
>
> - how to organize the workflow when using Fluid for templating? (since HTML guys might not know Fluid syntax)
> - is there a need for a templating system that would be a bridge between plain HTML templates and Fluid templates, in order for non Fluid guys to keep working on their templates after it has been "Fluidified" or is it ok to teach HTML guys about Fluid and rely on that?
> - If there is a need, how this templating system might be implemented? (i proposed a solution based on Firebug capabilities but i did not retain attention since it is browser dependant)
>
>
> My view on this questions is that yes, we need a kind of templating system that would allow non Typo3 aware staff to work on their HTML templates without bothering about how it is implemented.
> The goal here is to be able to change the design of the website without changing a single line of code in the HTML templates juste like classical Typo3 templating system allow to do.
>
> So, how to achieve that?
> Working with Typo3 nowadays, we can distinguish two types of templating :
> - templating used to build the structure of the website where we mostly inject content in pre-defined areas (subparts, markers, whatever you call them)
> - templating used in extensions where there is much more logic involved (loops, conditions and so on)
>
> IMHO there is a need for a mapping solution for the first type but not for the second one.
>
> This solution could be TV-like (but please without the XML overhead), or it could still rely on Typoscript (with or without a point and click wizard).
> It would take the HTML as input, parse it to add Fluid markers as defined in TV or Typoscript and feed it to Fluid Engine to do the final substitution.
> Of course, this step could be optional for Fluid trained people.
>
>
> What do you think?
>
> duch
>
>
>
> Le 23 mars 2010 à 18:10, Duch (aka. Grégory Duchesnes) a écrit :
>
>>
>> Le 23 mars 2010 à 08:51, Michael Sauter a écrit :
>>> But IMHO it is faster to learn FLUID. How long would it take to learn, say, 3 tags and how to output variables? 1 hour?
>>
>> I'm not sure we are talking about the same thing, Fluid is not just "3 tags and how to output variables", if you want to print the user manual, it is worth 30 pages...
>> It can be learned by an HTML guy but the learning curve will be longer than 1 hour believe me.
>>
>> see http://flow3.typo3.org/documentation/manuals/fluid/fluid.usermanual/ for details.
>>
>>
>> duch
>>
>> _______________________________________________
>> TYPO3-project-5_0-general mailing list
>> TYPO3-project-5_0-general at lists.typo3.org
>> http://lists.typo3.org/cgi-bin/mailman/listinfo/typo3-project-5_0-general
>
>
>