[TYPO3-ect] Ext-JS 1.0.1

[Joerg Schoppet]

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

Steffen Kamper wrote:
 > May be if there is a hook, a special extension could deal that
hooking that
> point and could be configurable, e.g. simple prevent imagelightbox:
> plugin.tx_pageheader.headerDataFromExt {
>   #no lightbox
>   kj_imagelightbox2_js_prototype = 0
>   kj_imagelightbox2_js_scriptaculous = 0
>  ...
> }
> 
> that is my vision.
> 
> vg  Steffen
Yes, such an extension would be cool, but once again, such an extension
have to make in some circumstances a "miracle"-decision.

Actually, I would see only one reasonable possibility:
There is one "master" extension, which sits above all the different
js-extensions:
- - script.aculo.us
- - ext-js
- - jquery
- - mootools
- - dojo
- - ...

Every extension, which wants to use a defined js-lib, registers itself
by the master-js-extension e.g. tx_masterjs::setPlugin('scriptaculous');

At the end, the master-js-extension is responsible to put all required
js-libs in the additionalHeaderData-array.


But this technique would require, that all ext-developers work together
and use one common ext to include there needed js-files.

This master-js-extension can grow in such a way, that the different
js-libs can register themself as service to this extension and that
client-extension can ask the master-js-extension, which js-libs are
available.

And at the top of the development-process, there stand the thought to
implement such a feature in the core ;-)


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

iD8DBQFGwUklq5Me6rRDqPURAmCpAJ0TVdLL2cLx4wkZN4QOee/5J+HpgwCdHvaL
MlEMZ//d6pbmtkl4QglZm3Q=
=p+ci
-----END PGP SIGNATURE-----