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

[Steffen Kamper]

"Elmar Hinz" <elmar.hinz at team.MINUS.red.DOT.net> schrieb im Newsbeitrag 
news:mailman.1.1176633501.23093.typo3-dev at lists.netfielders.de...
>#> That was easy. Now for a tetx menu item.
>>
>> TMENUITEM.allWrap
>> TMENUITEM.allStdWrap
>> TMENUITEM.wrapItemAndSub
>> TMENUITEM.beforeWrap
>> TMENUITEM.afterWrap
>> TMENUITEM.linkWrap
>> TMENUITEM.stdWrap
>> TMENUITEM.stdWrap2
>>
>> This is more complex and you cannot remove much:
>>
>> TMENUITEM.proc [allWrap]
>> TMENUITEM.submenuProc [wrapItemAndSub] TMENUITEM.textProc [stdWrap]
>> TMENUITEM.linkProc [linkWrap]
>> TMENUITEM.beforeProc [linkWrap]
>> TMENUITEM.afterProc [linkWrap]
>>
>
> Well much better, but with proc is an abbreviation. That is against the
> naming guidelines of v5. People can understand it with the help off a
> dictonary. Before they would ask what is has to do with Perry Rhodan.
> http://www.proc.org/ ;-)
>
> The coding guidelines say in short:
>
> 1.) Full words:
>
> Wrap is a full word.
> Proc is not a full word.
>
> 2.) Self explaining words:
>
> Wrap is a wrapper so it is wrong for processing.
> Proc is an abbreviation of programmers. Designers don't know it.
>
> 3.) CamalCase: both would be OK.
>
> Regards
>
> Elmar
>
>
Hi Elmar and all,

why not capsaling it, would be easier to understand for everybody, like

TMENUITEM.wrap.all
TMENUITEM.wrap.subMenu
TMENUITEM.wrap.link
TMENUITEM.wrap.beforeLink
TMENUITEM.wrap.afterLink

ok, now wrap is an object instead of string before, but this helps to 
understand the meaning of wrap without study the docs.

vg  Steffen
>
>
>
> -- 
> 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/
>