[TYPO3-ect] Introducing the controller as a register

[Daniel Brüßler]

Hello Elmar,

I think the more and more the logic is "glued together" using typoscript 
the more kickstarter will be very powerful, when it supports this.

this looks very cool:
do.1 = load
do.1.1 = keyOfTotalResultCount   // first parameter

Is there a pattern "content defined logic"? If that pattern exists, then 
it's that what we do here :-) Because TypoScript is a string, it is content.

Please define what you mean with "a register", I don't know this term. 
Is it a design-pattern?

thanks!

Daniel


Elmar Hinz wrote:
> Hi developers,
> 
> based on the vision of TS configurable actions, I introduce the controller
> as a register. This is easy, because the controller is an SPL object
> itself, so there is a register already build in. I use "TS notation" to
> show it:
> 
> submitAction {
>  ...
>  model = tx_my_model
>  model {
>    do.1 = load
>    do.1.1 = keyOfTotalResultCount   // first parameter
>    go.next = ...
>  }
>  ...
>  view = tx_my_viewWithResultBrowser
>  view {
>    do.1 = makeResultBrowser
>    do.1.1 = keyOfTotalResultCount  // first parameter
>    go.next = ...
>  }
> ...
> }
> 
> The regular content data is transported inside THE ARRAY of the SPL objects.
> Somtimes we need to transport some additional information along the SPL
> chain, for example the number of the total result count for the result
> browser. 
> 
> Such additional data kann be registered into the array of the controller by
> use of a key. Here we use the key "keyOfTotalResultCount".
> 
> The model registers the value. The view reads the register in a later step
> using the same key.
> 
> Regards
> 
> Elmar
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
>