[TYPO3-4-3] [TYPO3-core] RFC #13074: Feature: stdWrap for inclusion of CSS and JS files via pageRenderer

[Tyler Kraft]

>> Imagine a "chained reaction" like that:
> 
> Just another one:
> 
> 10 = TEXT
> 10 {
>     field = default_field
>     field {
>         override.field = editors_field_of_choice
>     }
> }
 >
> In this case, the editor would enter the name of the field to take the text
> from instead of the text itself.


But the editor doesn't have access to the TS, or not in my world at 
least. And isn't that already the case? ;-)

10=TEXT
10.field = editors_field_of_choice//default_field




> And another one:
> 
> 10 = CONTENT
> 10 {
>     table = defaulttable
>     table.override.field = individual_table
>     select {
>         max = 10
>         max.override.data = page:maxitem_field
>         where = colPos=0
>         where.override = colPos IN (0,1)
>         where.override.if.isTrue.data = page:usetwocolumns
>         begin.data = GPvar:tx_something|pagebrowser
>         begin.data.prioriCalc = intval
>     }
> }
> 
> Looks like this is the maximum of consistency AND flexibility we could get.

I, personally, think that is a great thing to be able to do (albeit it's 
complicated)

Ty