[TYPO3-dam-devel] RFC: #7676: Skin support

Uschi Renziehausen typo3news at otherone.de
Sat Dec 6 07:58:00 CET 2008


Hi folks,

if we are going to make tabs configurable we need to do it for 1.1!!!
Otherwise the editors Michael is concerned about will have to relearn 
DAM once 1.1 is installed. So this is a question of NOW or NEVER

Uschi

Dan Osipov wrote:
> Sure, I didn't know the styleSheetFile2 has another use.
> 
> I'll submit a bug report, and send a patch.
> 
> Dan Osipov
> Calkins Media
> http://danosipov.com/blog/
> 
> Michael Stucki wrote:
>> One problem which is introduced by this change, besides dropping tabs
>> completely(!)
>>
>> You set the stylesheet filename with $this->doc->styleSheetFile2.
>> However, this property should mainly be used by skins, and it may occur
>> that it's already set.
>>
>> Can you set it through the ->additionalHeaderData array instead?
>>
>> - michael
>>
>> Dan Osipov wrote:
>>> Hello everyone,
>>>
>>> This is a SVN patch request.
>>>
>>> Affected Extension: tx_dam version 1.1-dev
>>>
>>> BT reference: http://bugs.typo3.org/view.php?id=7676
>>>
>>> Branches: trunk
>>>
>>> Problem: DAM doesn't use Typo3 skin.
>>> * Add docheaders to the DAM modules, like the new core modules in 4.2
>>> and also use the full width
>>>
>>> Solution: This is a first in a series of patches for this issue. What it
>>> does is modify the code a bit to use the Typo3 4.2 skin. It makes it
>>> look better on 4.2.
>>>
>>> A few icons have been moved up to the docheader. The tabs have been
>>> placed into the function menu - tabs didn't look good in the new skin.
>>> Currently the existing Typo3 info.html template is used, however in the
>>> future we might use our own template.
>>>
>>> Comments are welcome.
>>>
>>
>>


More information about the TYPO3-team-dam mailing list