[TYPO3-ect] Future of different AJAX-libs?

[Martin Kutschker]

Elmar Hinz schrieb:
> R. van Twisk wrote:
> 
>>Joerg Schoppet wrote:
>>
>>>Hi all,
>>>
>>>I just want to ask the above question.
>>>
>>>Actually I see the following progress:
>>>
>>>Here, in the ECT, XAJAX is promoted. There are even some exts, which
>>>build on it.
>>>  
>>
>>To be honest, I think most of the promotion comes from you,
>>which is ok of course.... Before the was xajax, there where already many
>>other options. I have been working with jpspan a lot.
>>
> 
> 
> Hi,
> 
> I have never heard of jpspan before your posting. :-) There are so many
> php/js libraries popping up theese days, some of them with really nice
> functionalities. It would be a mistake if the ECT team would fix
> ultimatively upon one of them. It also would be a mistake if ECT
> wouldn't give any recommendation within this jungle.
> 
> I think we officially should promote xajax constantly for some period
> until there comes up a significant better alternative or until we have
> an own TYPO3 ajax service available, that can offer similar functionality.
> 
> There are three good reasons to promote xajax for now:
> 
> 1.) It does the job well
> 2.) It is available and maintained as a stable TYPO3 extension.
> 3.) There is a tutor extension available for it.
> 
> We still can't say all of this for other libraries.

This is spoken from an extension view. What do you suggest for the Core? I 
don't think that TYPO3 should switch again and again. So a choice for one 
library is not for good but certainly for a long period.

Is it worth that those new Core parts that use prototype to be converted to 
XAJAX? If yes, shall the XAJAX extension become a system extension?

Masi