[TYPO3-project-4-3] Header / Footer class for BE and FE

[Martin Kutschker]

Steffen Kamper schrieb:
> Hi Masi,
> 
> Martin Kutschker schrieb:
>> Steffen Kamper schrieb:
>>>     # this code is wrapped in Ext.onReady-Block
>>>     inlineJSExtOnReady {
>> [snip]
>>>    }
>>
>> As other JS frameworks have similar concepts I wouldn't a) change the
>> name (like inlineJSonDocumentReady or maybe even more general
>> inlineJShandler.documentReady, allows for inlineJShandler.load, .unload,
>> .resize, .textResize, etc)
>>
> 
> yes. As this is a draft, fine tuning will follow. My first aim was to
> use existing methods, after it can be generalized.

In case it goes to the Core: please generalize before 4.3 is shipped.

>>> There is also a parameter which moves all existing Javascript to end of
>>> page:
>>> config.swapJsFromHeaderToFooter = 1
>>
>> Why? BTW, "swap" means to "change places" so this property name implies
>> that any code in the footer is moved to the header.
> 
> i'm open for better naming. Should read "move", yes.

I still wonder why I would need that property.

>>> config.concatenateJSandCSS
>>
>> What should happen if implemented?
>>
> 
> all js files will be concatenated in one js file to reduce load requests.
> Same for the css files.
> 
> Inline parts will be written in the concatenate file as well.

May I declare parts to be real inline? I mean I may want to add some
general code (which should be moved to an external file), yet want to
add JS code that is page specific. If everything is moved to external
files I end op with a multitude of them.

Masi