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

[Martin Kutschker]

Elmar Hinz schrieb:
> 
> 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>

I don't get it why we need a "process" and a "wrap". A wrap is simply a 
processing like any other.

temp.foobar.value.process.10.wrap = <em> | </em>
temp.foobar.value.process.20.noTrimWrap = |label:    |.|

You can even have this:

temp.foobar.value.process.10.wrap = | + |
temp.foobar.value.process.10.wrap.splitChar = +

(though I would name it "separator" or "delimiter")

I wouldn't change the current "wrap" (adding the array feature). I think 
this is more confusing then adding *one* new property.

> But we run into troubles as soon if we want to do a processing including
> the wrappers:
> 
> temp.foobar.value.process.30.tagsToUpperCase = 1    ???

What's different to ...

> 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

...this? You changed the 30 to 50, but that isn't significant.

Masi

PS: Who needs a tagsToUpperCase? In XHTML all tags a only valid in 
lowercase.