[TYPO3-core] RFC #15928: Replace the current if-construct of stdWrap with real functions and make each of them stdWrap aware

[JoH asenau]

This is an SVN patch request.

Type: Feature

Bugtracker references:
http://bugs.typo3.org/view.php?id=15928

Branches:
Trunk

Problem:
function stdWrap is using a huge series of if clauses
Each of the stdWrap functions should be stdWrap aware itself

Solution:
As decided during the "Pimp my TS" workshop at T3DD10 and as announced at T3CON, the attached patch will do the following:

1. Remove the serialized if clauses from the function stdWrap
2. Replace them with real functions called in the correct order to stay backwards compatible
3. Make each of the functions stdWrap aware
4. Still take care of the 4 hooks currently available in function stdWrap

Exceptions for 3:

cObject and the recursive stdWrap call will not use nested stdWrap functions, since these are the only functions using stdWrap functions on the real content, while all others will apply stdWrap functions to the value of the property itself
preUserFunc, postUserFunc and postUserFuncInt are excluded form nested stdWrap as well to avoid conflicts with individual markup used within those functions

I made some tests with default CSS-styled-content elements and everything seems to be running quite well. Admin Panel shows that the new version seems to be a bit faster than the original, although the nested function call is already implemented.

Cheers

Joey

-- 
Wenn man keine Ahnung hat: Einfach mal Fresse halten!
(If you have no clues: simply shut your gob sometimes!)
Dieter Nuhr, German comedian
Xing: http://contact.cybercraft.de
Twitter: http://twitter.com/bunnyfield
TYPO3 cookbook (2nd edition): http://www.typo3experts.com
-------------- next part --------------
A non-text attachment was scrubbed...
Name: stdWrap.diff
Type: application/octet-stream
Size: 75213 bytes
Desc: not available
URL: <http://lists.typo3.org/pipermail/typo3-team-core/attachments/20101007/b2970a98/attachment-0001.obj>