[TYPO3-ect] TODO

[Steffen Kamper]

"Elmar Hinz" <elmar.DOT.hinz at team.MINUS.red.DOT.net> schrieb im Newsbeitrag 
news:mailman.1.1169900585.29537.typo3-team-extension-coordination at lists.netfielders.de...
> Am Sat, 27 Jan 2007 11:34:19 +0100 schrieb Daniel Brüßler:
>>
>> Only problem maybe: When there're many functions who want to register
>> between 190 and 200 (when the 190 is something very important) we would
>> have something like a traffic-jam. ;-)
>>
>
> Well, we should ask a 15 year old child for a solution.
>
> It's floats in german notation. Maybe the TS parser would need a litle fix
> to support that.
>
> xyAction = ACTION
> xyAction {
>        ....
> 198 = SPL
>        198.class = tx_myext_classX
>        198.configurations {
>          ...
>        }
> 198,5 = SPL
>        198,5.class = tx_myext_classX
>        198,5.configurations {
>          ...
>        }
> 199 = SPL
>        199.class = tx_myext_classY
>        199.configurations {
>          ...
>        }
>        ....
> }
>
>
>

Hi Elmar,

nice idea.
In my Eyes this is normally the concept of service, where you have the 
priorities for overwriting. the services also have the possibility of 
fallback.
With typoscript it can be complicated
- no fallbacks
- easy to overwrite, also easy to corrupt by user with misconfiguration

Also for this you have to extend functionality of Typoscript.

So my question - why not using services and service chains ?
May be i'm influenced by the cal project, where this service principe is 
used.

vg  Steffen