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

[Elmar Hinz]

Michael Scharkow wrote:
> 
> The one good (IMHO) thing about prototype is that it adds a lot of
> convenience to JS functions, like iterating over objects, etc. in a way
> that is familiar to most programmers. If you need hardcore DOM
> manipulation, you have to understand JS anyway, even when using xajax.
> 

I have no doubt that prototype is a powerfull library, else it wouldn't
be such successfull. But it requires JS knowlage.

> 
> Using protoype would make it *very* easy to keep up with the upstream
> version because it is essentially one single JS file.
> 

That is true. No messages about invalid classnames or misseing XCLASS
footers. I wonder why nobody has published a prototype extension. Maybe
the license doesn't match?

>> I don't need all this goodies to simply display a menu tree. In this
>> case performance is the most critical factor. A specially tailored
>> version of ajax would still be the best solution for such critical tasks.
> 
> Displaying a menu tree does not involve much work with most AJAX libs,
> and if we include prototype.js in all BE output, it will be cacheable
> and not cost much performance.
> 

The point is that I dream of a BE that is so slim, that I don't need to
turn caching on at all. There are lots of pitfalls if you turn caching
on during developement.

Regards

Elmar