[TYPO3-hci] typoscript issues

[Sudara Williams]

Interesting thought!

...it might be 2+ years to get to Typo3 5.0.

Maybe it is worth the few hours to go through the 4.1 source and  
'fix' the inconsistent names by providing consistent aliases.

We can also think of this as "getting ready" for 5.0 by making 4.x as  
solid as possible, and basing the 5.0 API on the solid 4.x branch.

camelCasing is one issue. The other big one is understandability -  
there are some funky obscure names floating around!

patches to the core! patches to the core!

sudara



On May 7, 2007, at 4:15 PM, Martin Kutschker wrote:

> Martin Holtz schrieb:
>> hi,
>>
>> is it possible to add an function
>> aTagParams to typolink? (instead of ATagParams)
>>
>> The most functions in Typoscript are camelCase, but that function  
>> is not. I
>> think it would be the right way, to change all that functions - it  
>> should
>> not be very difficult - or am i wrong?
>
> The naming of Typscript properties and functions is not consistent.  
> Tag
> related properties are often in upper case as is ATagParams.
>
> I think it makes sense to unify the names, but only in context with
> TypoScript 2.0 of TYPO3 5.0. So once the names of TS 2.0 (and use a
> consitent naming scheme) are stable we can start a transition for  
> TYPO3
> 4.x. Adding the new names as aliases for the old and then  
> deprectaded names.
>
> Masi
> _______________________________________________
> TYPO3-team-hci mailing list
> TYPO3-team-hci at lists.netfielders.de
> http://lists.netfielders.de/cgi-bin/mailman/listinfo/typo3-team-hci
>