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

[Elmar Hinz]

Joerg Schoppet wrote:
> Person1: We implement a new page-tree with prototype.
> 
> My dream ;-) would be, to have the strengths of both approaches combined:
> The easy of use of XAJAX for php-programmers and the different effects
> of prototype.
> 
> Comments?
> 
> Joerg Schoppet

Hi Joerg,

I think both approaches can perfectly live side by side. I have no clue
how they could be combined. Even the author of xajax uses xajax side by
side with prototype, like hi posted in the xajax forum. The functional
range of xajax is limited to every days tasks. But:

* Programmers that don't want to fiddle around with javaScript will use
xajax.
* Programmers that want quality by prevention of errors in javaScript,
will use xajax, because javascript is fully autogenerated.
* Programmers that wish a slim library can use xajax.
* Programmers that want a high production rate will use xajax.

So I am sure xajax will still stay for a while, until it will be
replaced by somthing, that provides the same advantages, but is still
ahead. Prototype doesn't provide this advantages. As you say it is not a
direct competitor. Rather an addition to solve more complicated tasks.

I have some doubts that fat prototype is the best possible decision for
the heavy used functions of the BE. I would take a very slim library
with a slim data format, rather not XML, maybe JSON.

However, those who do the work, also make the decisions, for good or
bad. That's a central rule in open source.

Regards

Elmar