[Seaside] Dumb Question: How to render new state after ajax
jfitzell at gmail.com
Wed Nov 4 22:12:10 UTC 2009
And to be clear, if you really want, you should be able to use #show:
within an ajax callback, just not #call:. You should also be able to
use #answer: as long as the component was displayed with #show: and
not #call:. But of course, you'll still have to reload the page if you
want to see the result.
Doing a call in an ajax callback makes little sense because it would
abort the callback without you being able to generate a response
(normal callbacks redirect to another URL which generates the HTML
On Wed, Nov 4, 2009 at 1:30 PM, Boris Popov <boris at deepcovelabs.com> wrote:
> If your ajax callback will be forcing a full refresh, aren't you better off
> just doing a regular callback?
> -Boris (via BlackBerry)
> From: seaside-bounces at lists.squeakfoundation.org
> <seaside-bounces at lists.squeakfoundation.org>
> To: Seaside - general discussion <seaside at lists.squeakfoundation.org>
> Sent: Wed Nov 04 13:16:51 2009
> Subject: Re: [Seaside] Dumb Question: How to render new state after ajax
> 2009/10/15 Karsten <karsten at heeg.de>
>> Hi Richard,
>> you can't do that with Ajax easily. The problem is that during an AJAX
>> callback you're actually rendering and not in the normal callback phase.
>> You could however register a callback that does the answer and send
>> url. However, that's a bit tricky :-)
> Why It can not be implemented in simplest, user transparent way as Richard
> wrote? Or it can?
> I think it's really usefull stuff.
> seaside mailing list
> seaside at lists.squeakfoundation.org
More information about the seaside