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

[Elmar Hinz]

> 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

Another advantage would be that it reads more like human grammer in the
sense of: 

TMENUITEM, wrap it all.
TMENUITEM, wrap the link.

One could go to extremes:

TMENUITEM.wrap.itAll
TMENUITEM.wrap.theSubMenu
TMENUITEM.wrap.theLink
TMENUITEM.wrap.itBeforeTheLink
TMENUITEM.wrap.itAfterTheLink

But that probably results in to much typing.

StdWrap shows the dilemma of wrap. Soon you want to process not only to
wrap. TMENUITEM.wrap.itToUpperCase? That doesn't give sense.

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. ... = ...

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/



























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