[TYPO3-dev] RFC:s standard processing property as stdWrap replacement

[Elmar Hinz]

>> The best solution IMHO would be to really work with two objects/functions.
>> One for processing the value and one for wrapping it. That would bring 2
>> advantages.
>> 
>> a) It is more logical to understand.
>> b) It results in smaller classes and functions on level of PHP.
>> 
>> XYZ.process. ... = xxx
>> XYZ.process. ... = yyy
>> 
>> XYZ.wrap. ... = xxx | yyy
>> XYZ.wrap. ... = ...
>> XYZ.wrap. ... = ...
> 
> 
> What's wrong with this?
> 
> XYZ.process.10.wrap = yyy

It was loud thinking in a different context, the special context of
Steffen's example.

To transfer this to the original context we could think of:

temp.foobar = HTML
temp.foobar.value.process.10.getData = date : U
temp.foobar.value.process.20.stringForTime = %A %e. %B %Y

temp.foobar.value.wrap.10.trim = <em> | </em>
temp.foobar.value.wrap.20.noTrim = <p>Time: | </p>

But we run into troubles as soon if we want to do a processing including
the wrappers:

temp.foobar.value.process.30.tagsToUpperCase = 1    ???

So it's necessary to have one processing array:

temp.foobar = HTML
temp.foobar.value.process.10.getData = date : U
temp.foobar.value.process.20.stringForTime = %A %e. %B %Y
temp.foobar.value.process.30.trim = <em> | </em>
temp.foobar.value.process.40.noTrim = <p>Time: | </p>
temp.foobar.value.process.50.tagsToUpperCase = 1

Regards

Elmar

-- 
Fight the no_cache parameter:
http://t3flyers.wordpress.com/2007/04/06/a-quick-guide-to-proper-caching-with-tslib_pibase-episode-1/
http://t3flyers.wordpress.com/2007/04/06/a-quick-guide-to-proper-caching-with-tslib_pibase-episode-2/