[Typo3-dev] Order of stdWraps

[Kasper Skårhøj]

This is certainly a deficiency of stdWrap / TypoScript, but changing the
order is generally out of question because the implications for peoples
websites will be totally unpredictable. Therefore you will see that
rather the list of properties for stdWRap has continuously been extended
to - what - some 10 different types of wrap for instance - to
accommodate this need.

Maybe it would be better to design a stdWrap property which will
dynamically process content. SOmething like:


stdWrap.proc = crop(listNum($$$VALUE$$$,0,"X"))

The "functions" will of course be a pre-defined list of functions we
implement. With a clever syntax it might even be fast (depends on how
quick the string can be parsed on the fly.

- kasper



On Thu, 2005-03-31 at 15:38, Michael Stucki wrote:
> Hello,
> 
> in the last few days I often had problems with stdWraps being executed in a
> not so optimal order.
> 
> Example:
> mytext.crop = 22 | X | 1
> mytext.listNum = 0
> mytext.listNum.splitChar = X
> 
> Unfortunately this does not work because crop is handled after the listNum
> property.
> 
> Questions are:
> - How do you handle this? (I hate to nest cObjects only for this)
> - Should we think about the order of these statements?
> - In this special case: Is there any reason for not moving "crop" right
>   before "splitChar"?
> 
> Regards, michael
-- 
- kasper

*******************
Happy new year! - My email address is now: 

		kasper2005 at typo3.com