[TYPO3-50-general] New templating system?

Michael Sauter mail at michaelsauter.net
Mon Mar 22 13:38:07 CET 2010

On 22.03.10 11:39, "Duch (aka. Grégory Duchesnes)" wrote:
> - this solution is "fully useful" without the firebug extension, it is just a helper
> - we are talking about templating here, therefore not about contributors with limited rights (both on their computers and Typo3) but admin users.
> Beside this considerations, did you have a look at the video?
> duch
> Le 22 mars 2010 à 10:47, Denyerec a écrit :
>> On Sun, 21 Mar 2010 17:10:01 -0000, Duch (aka. Grégory Duchesnes)<typo3 at ilomedia.net>  wrote:
>>> It is based on an extension that only focuses on the mapping (when TV also deals with the look of the back-end and allows to create new types of content called FCE) + a Firebug extension (which you can consider as a wizard).
>> Given that a large number of corporates do not adopt Firefox for support, liability and intranet-application-compatibility issues, I would be surprised if any solution that required or leveraged a particular browser's plugin architecture to be fully useful would become the standard :(
>> Den

I had a look at your video, nice idea!

But I think this is way too complicated. This is not because of your 
implementation, but due to the whole concept of templating. I think we 
need to change that completely, and I think FLUID fits perfectly ;)

First off, I don't get why you need something like TypoScript for 
templating. In my eyes, you get enough flexibility if you can build a) a 
page grid (like that proposed during UX09) and b) insert "custom 
elements" inside (like FCEs in TV). If you can do that, you can do 
everything. Of course, the configuration/backend of this could be done 
via TypoScript, but IMHO the admin should be able to do this without 
writing TypoScript.

Secondly, I think XML is the wrong path as well ... very much overhead 
and hard to edit manually.

Now, the main question for me is how to build the "custom elements" (the 
mapping from fields to DOM). I would suggest getting rid of the idea of 
"mapping" in the first place.

What about the following approach:

- "Custom elements" are based on models + FLUID templates.
- If you create a new "custom element", TYPO3 generates a new content 
model (inherting from an abstract model) from the template you specify.
- How does this work? The template contains special viewhelpers, which 
serve 3 different purposes, depending on the context they are used:
1)"creating the model": the template is parsed and the viewhelpers get 
converted into properties of the model.
2) "creating/editing content": the template is parsed and the viewhelper 
get converted into form elements
3) "frontend mode": the tags get converted into the model values

This lets you create fully customizable elements very easy (I think the 
idea is really really simple ...). You only need to know how to use 
FLUID and which widgets (textfield, textarea, picture uploader etc.) are 
I haven't tried to implement this in FLOW3 yet, but I think this should 
be fairly easy (maybe the parsing of the template to generate the models 
it is a bit more complicated, but you could also do this approach 
without this automation). Anyway, I'm thinking about hacking together a 

This approach could even be used to do the page grids ...

What do you think?
BTW: If this is not the course taken for v5, I'm very excited about 
something that is even better! :)

More information about the TYPO3-project-5_0-general mailing list