[TYPO3-ect] Merging fhlibrary into tx_lib: pi_getSetupOrFFvalue
R. van Twisk
typo3 at rvt.dds.nl
Tue Aug 29 20:23:00 CEST 2006
Jan-Hendrik Heuing [DD] wrote:
>> Franz proposes to merge fh_library into tx_lib/tx_div. A good idea, but
>> lets look at some details first and give us your opinions:
>>
>
> Good, but:
>
>
>> function getSetupOrFFvalue(&$pibase, $code, $codeExt, $defaultCode,
>> $T3FlexForm_array, $fieldName='display_mode', $useFlexforms=1,
>> $sheet='sDEF',$lang='lDEF',$value='vDEF') {
>> $rc = '';
>> if (empty($code)) {
>> if ($useFlexforms) {
>> // Converting flexform data into array:
>> $rc = $pibase->pi_getFFvalue($T3FlexForm_array,
>> $fieldName, $sheet, $lang, $value);
>> } else {
>> $rc = strtoupper(trim($pibase->cObj->stdWrap($code,
>> $codeExt)));
>> }
>> if (empty($rc)) {
>> $rc = strtoupper($defaultCode);
>> }
>> } else {
>> $rc = $code;
>> }
>> return $rc;
>> }
>>
>>
>> My first idea is, that this function should be splitted, cause it
>> servers different tasks.
>>
>
>
Isn't that work already handled by api_macmade? I use it all the time
for my extensions.
Ries
> I don't get it, what is this about? Maybe I am being stupid at the moment,
> what is the purpose?
>
>
>> Questions: Is there a function to Merge Setup and Flexforms recursively?
>>
>
> Do I get it right that you talk about something which reads setup-values as
> well as content-plugin related values, one takes precedence after the other
> and such?
>
>
> Sorry, for being stupid. Luckily that happens not too often ;)
>
> JH
>
>
> _______________________________________________
> TYPO3-team-extension-coordination mailing list
> TYPO3-team-extension-coordination at lists.netfielders.de
> http://lists.netfielders.de/cgi-bin/mailman/listinfo/typo3-team-extension-coordination
>
--
Ries van Twisk
Freelance Typo3 Developer
=== Private:
email: ries at vantwisk.nl
web: http://www.rvantwisk.nl/freelance-typo3.html
skype: callto://r.vantwisk
=== Work:
email: ries at livetravelguides.com
web: http://www.livetravelguides.com
More information about the TYPO3-team-extension-coordination
mailing list