[TYPO3-ect] general approach for JS

[Joerg Schoppet]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Steffen Kamper wrote:
> Hi,
> 
> while studying the Yahoo rules for speed optimization [1] (especially Rule 
> #6) JS should be moved to the bottom.
> I know that is not possible all the time, but the libs are included in TYPO3 
> in head. If i use extensions, i have no possibility to influence this.
> 
> So i come to the conclusion, that the best thing would be a general 
> JS-Collector Object. There all JS could be collected and rendered by 
> pagegen-script.
> My wishes for that would be
> - categorization (include a lib/snippet, may be some standards for standard 
> libs e.g. mootools, prototype etc.)
> - configuration with TS to allow enable/disable including for some pages
> 
> e.g. there is image lightbox, which includes prototype etc. It's only 
> necessary on pages where pictures are defined as lightbox images, other 
> pages don't need this inclusion.
> there is ExtJS inclusion but is only needed on pages having ExtJS widgets.
> etc...
> 
> I will start a proof of concept for this and would be glad if you could 
> write your ideas / proposals.
> 
> vg  Steffen
> 
> 
Hi Steffen,

this sounds very interesting.

Some times ago I also thought about such a container-extension.
Additionally I wanted to implement a nice BE-interface to manage the
different js-libs:
- - jQuery
- - prototype
- - script.aculo.us
- - YUI
- - Ext

I though about a standardized api, each extension can simple "say" I
need the following libs "..." and after all extensions on a page have
requested there libs the management-extension is responsible for the
right inclusion.

What do you think about this additional feature?

Regards

Joerg Schoppet
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.6 (MingW32)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org

iD8DBQFG5ir5q5Me6rRDqPURAqCMAJ9HQkbw0MTK2ZVt94vO8o33qKf4hgCgpAZx
T5ZrNJ7KsP07XNGz1s+alRg=
=EMe1
-----END PGP SIGNATURE-----