[Seaside] [Q] Seaside, SeasideAsync, Scriptaculous?

[Philippe Marschall]

> As Lukas wrote - SeasideAsynch is the first attempt at an Ajax solution
> - based on the "old" rendering API, which still is the default one
> though. A component decides which API to use by implementing
> rendererClass, check references to WARenderCanvas to find components
> written for the new API - I noticed that ShoreComponents are written
> against the new Canvas API so I looked at that code for some hints.
>
> Scriptaculous is the new Ajax attempt based on the Canvas API.
>
> So in short - use Seaside2a3 with WARenderCanvas with Scriptaculous. :)

SeasideAsync works with the Canvas API as well.

For beginners I recommend starting with SeasideAsync because it's way
simpler to the something working.

Cheers
Philippe