[TYPO3-ect] general approach for JS

[Daniel Brüßler]

Hello Steffen,

I found an extension what has this topic: moo_fx

When the HTML-code has to be parsed it's bad for the performance. So
pid-lists for inclusion or removal are better. JS-files, CSS-files and
the order in which the inclusions should be done. Easier to use is a
selectbox in the page-record. When I used Adobe Spry I just used one
widget what needs it's widget-CSS-file for the start-page. My
TypoScript-dataset-entry for this has the name "Adoby Spry
Transparent-Effect". I don't find it good when a JS-framework-Ext
integrates the code for every page using the adddionalHeaderData-Array.

kind regards
Daniel


>> I just have an entry in "TypoScript Template Storage" for the
>> javascript-includes. On pages/ subtrees where I need it I just add this
>> entry in "Include basis template". So the performance is good.
>> Why don't you use that way?
> i want to do it simular. But most extension use the additionalHeaderData to 
> include their scripts.
> I think a special extension is needed which hooks the pagegen and is 
> configurable with pidlists /excludelists in TS, something in this way.
> Anyway, please drop your ideas here ;-)
> vg  Steffen