[TYPO3-ect] TS Action chains for SPL objects

Franz Koch typo.removeformessage at fx-graefix.de
Wed Aug 8 09:50:21 CEST 2007


Hi Elmar,

> defaultAction {
>   START = model
>   model = tx_bananas_models_board
>   model.do.1 = load
>   model.go.next = view
>   view = tx_bananas_views_list
>   view.do.1 = render
>   view.do.1.1 = listTemplate
>   view.go.next = translator
>   translator = tx_lib_translator
>   translator.1 = translateContent
>   translator.return = content
> }

This looks very interesting. But wouldn't it be more flexible to use a 
numbering by ten (like suggested for TS) for the action 'commands' like:

------
defaultAction {
	START = model
	model = my_model
	model.do {
		10 = load
		10.1 = param1
		10.2 = param2
		20 = whatever
		20.1 = param1
	}
	model.go.next = view
	...	
}
------

it would allow to reuse most of the TS when extending the default 
behaviors of a extension, because you can place some calls in between.


Do you think the TS action chains could somehow be used to simply add 
custom-fields/-marker to the rendering scope of any extension? I wonder 
how that could work. Ok, you can create your own model and change the 
according TS value - but what if you have 2 extensions extending the 
same extension/model that don't know of each other. Then you probably 
can't combine them?
I'd like lib/div to become a extension-'framework' that makes every 
extension as flexible as it could be by default. So that no 
'modified_ext_xy' appears in TER in future but only 'extension__addon_1' 
and so on.

--
Kind regards,
Franz Koch


More information about the TYPO3-team-extension-coordination mailing list