[TYPO3-content-rendering] [Typo3-dev] Re: Smart Content Rendering
Martin Kutschker
Martin.Kutschker at n0spam-blackbox.net
Mon Oct 24 12:48:18 CEST 2005
JoH schrieb:
>
>
> Yes - and the magic word is: "templated wraps" + optionSplit
> If there was the possibility to select the part(s) that is/are used as a
> wrap from a template all the possible problems you described above could be
> solved.
>
> For example in a menu you could do something like this:
>
> allWrap.fromTemplate = 1
> allWrap =
> |*|NEWROW1||1COL||1COL||LASTCOL||NEWROW2||1COL||1COL||LASTCOL|*|NEWROWLAST||
> 1COL||2COL
>
> NEWROWX and XCOL could be defined in the template.
AAAAAAHHHHHHHHHHHHHHHHH!!!!!!!!!!!!!!!!!!!!!
Introduce option splits whereever you like, but don't force them upon
the poor admins as the true TS way of templating.
Masi
PS: More and more I'm convinced that the backwards compatibility with
old "content default" is a major block for the developing of anything.
It demands options and twists for everything, even if we all agree it
should be deprecated.
More information about the TYPO3-project-content-rendering
mailing list