[Seaside] Re: WATask & Ajax questi
renggli at gmail.com
Fri Nov 16 15:52:17 UTC 2007
> Any idea if something like this is in the works? Until then, any hints on
> how to take advantages of components/#call without losing Ajax?
Not that I know of. The current model of Seaside does not allow to do
that kind of things easily. One reason for this is that component
boundaries cannot be identified clearly in XHTML. Seaside cannot know
what parts of a page change due tue a #call: or #answer:. Moreover it
is ambiguous how backtracking should work in an AJAX application.
Building AJAX heavy applications in Seaside is truly painful. AJAX
does not work together with replacing children and the #call:/#answer:
Seaside and AJAX work well together for small status updates of an
existing component tree. Also enhancing the user experience by
providing sophisticated widgets or submitting and updating forms works
More information about the seaside