[TYPO3-ect] new design for js-extensions?

[Joerg Schoppet]

Steffen Kamper wrote:
> "Joerg Schoppet" <joerg at schoppet.de> schrieb im Newsbeitrag 
> news:mailman.1.1194260524.11546.typo3-team-extension-coordination at lists.netfielders.de...
>> Hi,
>>
>> actually I'm in progress of redefining the js-extensions, which are
>> under my responsibility:
>> - extjs
>> - jquery
>> - script.aculo.us
>>
>> In the future releases I want to add the possibility to decide, which
>> version of the respective library should be used.
>>
>> A great inspiration was the extension nano_jquery by Bjoern Ellebrecht.
>>
>> So here is my question:
>> Should the future extension be only configurable over a static-template,
>> like the one in nano_jquery?
>> Should the future extension be only configurable over programming, like
>> actual?
>>
>>
>> Hope to see some answers! ;-)
>>
>> Regards
>>
>> Joerg Schoppet
> 
> Hi Joerg,
> 
> as you know i also think about a common solution, also for integrating JS in 
> page for general.
> 
> I think it's not very useful if the extension provide the library, as the 
> author of the extension is responsible for all the updates.
> An idea would be:
> One folder containing the libs
> jslibs
>  - jquery
>  - mootools
>  - extjs
> ....
> and the extension handles the interface for the lib, makes the includes and 
> the settings in an easy way.
> So the user can update the lib by himself if any update is available and is 
> independent from the extension.
> 
> In general i think about a general core patch about including JS, handling 
> includeJS and headerData, maybe JS should be included all the time with 
> includeJS so there is the possibility to integrate it at bottom of document 
> body.
> 
> vg  Steffen 

Hi Steffen,

I still remember the discussion, but actually I have to say: I've not
the time to think about such an extension (BUT I find it extremly usefull).

One step I this direction would be the first approach, I've suggested
(nano_jquery).

With this, you define on a page-level, which js-libs in which version
you want to use. You can have multiple extensions on a page, which need
e.g. extjs. Additionaly you can set on page A a plugin, which requires
extjs 1.1 and on page B you can set a plugin, which requires extjs 2.0.

As already said, this would be the first step. The next step would be an
extension, to which all js-lib-extension can register and then you can
define on page-level, which js-libs in which version should be included.

It doesn't sound really complicated, mmmmh!?!


Regards

Joerg