[TYPO3-dev] BEenableFields (add)

[Steffen Kamper]

"Martin Kutschker" <Martin.Kutschker at n0spam-blackbox.net> schrieb im 
Newsbeitrag news:mailman.1.1180023226.7914.typo3-dev at lists.netfielders.de...
> Steffen Kamper schrieb:
>> "Dmitry Dulepov" <9f4eetb02 at sneakemail.com> schrieb im Newsbeitrag 
>> news:mailman.1.1180017987.18065.typo3-dev at lists.netfielders.de...
>>> Martin Kutschker wrote:
>>>> He asks for the reason of this. Why do you have to call a seperate 
>>>> function?
>>> I also had the same question (it is very different from FE expereince 
>>> where it is all in deleteClause()). However I accept is as that we have 
>>> such API... May be for reason, no idea.
>>>
>>> -- 
>>> Dmitry Dulepov
>>>
>>> Web: http://typo3bloke.net/
>>> Skype: callto:liels_bugs
>>>
>>> "It is our choices, that show what we truly are,
>>> far more than our abilities." (A.P.W.B.D.)
>>
>> thx for the answers, but they doesn't satisfied me :-)
>> API can change when rest of code is changed. If there are obsolete parts, 
>> why never touch ?
>> A seperate call for deleted only is too much as i can write it " and 
>> deleted=0" - i asked to keep it as simple as possible.
>
> Other question: why have different functions in various places that do the 
> same for BE and FE? Sometimes they really do the same, somtime only 
> nearly...
>
> Masi

in this case it make sense cause don't care of fe_user / group.
But function could recognize BE /FE by itself. Then tslib_content would not 
be the right place.
And right, in this case it's TCA-specific and i would wish a central place 
for these.

vg Steffen