[TYPO3-core] RFC: #6259 Disabling Tabs with no fields (does not work)
Tapio Markula
tapio.markula at xetpoint.fi
Sun Nov 18 12:33:23 CET 2007
Malte Jansen kirjoitti:
> Tapio Markula schrieb:
>>
>> In fact it would be better to separate this function as own function
>>
>> as generic class file into t3lib
>> class.t3lib_dyntabmenu.php
>>
>> in template.php would be just reference
>>
>> function
>> getDynTabMenu($menuItems,$identString,$toggle=0,$foldout=FALSE,$newRowCharLimit=50,$noWrap=1,$fullWidth=FALSE,$defaultTabIndex=1,$dividers2tabs=1)
>> {
>>
>> t3lib_dynTabMenu::getDynTabMenu($menuItems,$identString,$toggle,$foldout,$newRowCharLimit,$noWrap,$fullWidth,$defaultTabIndex,$dividers2tabs);
>>
>> }
>>
>> in t3lib_tceforms.php could use also references to this function.
>> JavaScript could be externa JS-file and as compatibility reasons the
>> function could be
>> /**
>> * Returns dynamic tab menu header JS code.
>> *
>> * @return string JavaScript section for the HTML header.
>> */
>> function getDynTabMenuJScode() {
>> return '<script type="text/javascript"
>> src="'.t3lib_div::getIndpEnv('TYPO3_SITE_URL').PATH_t3lib.'getDynTabMenuJScode.js"></script>';
>> }
>>
>> with that path it should work both in backend and frontend.
>>
>> I try to create patch proposal to use function getDynTabMenu in all
>> situations
>> * backend
>> * frontend editing
>> * frontend plugins
>
> It does not belong to this patch.
> Moving functions etc. belongs to a new patch...
done
[TYPO3-core] Tabbed menus as a separate class file
I recommend that we could start making new patches for tabbed menus
after we first separate it into own class
More information about the TYPO3-team-core
mailing list