[Seaside] Handling redisplay/update stuff

Tim Rowledge tim@sumeru.stanford.edu
Mon, 27 May 2002 22:51:55 -0700

Avi Bryant <avi@beta4.com> is claimed by the authorities to have written:

> I'm not sure I'm entirely clear on what you're asking.  You want to submit
> a form, but not have the browser reload anything?  The only way to do
> that is with nasty javascript tricks involving the form submitting to a
> hidden frame; trust me, you don't want to go there.
Oh, pity. Yes that was pretty much what I was thinking; since submitting
the form doesn't go anywhere new I was imagining it would be possible to
just tell it 'nothing changed'. Silly me.
> If you have a complex page and redrawing the whole thing is a problem, you
> could split it up into a few html frames; only the frame with the actual
> questions would have to reload.  That is, you could if Seaside had a frame
> element; if you really need one, I can throw it together for you tomorrow.
> But I hate framesets.
Not keen on them myself. The page is very simple but saving cycles is
good. One day we will be able to cache saved cycles and get them all in
a rush when we really need them for Doom XXIV; return to the son of the
bride of the thing.
> As for re-randomizing the answers, there should be lots of ways around
> that - for example, do the randomization in the question's setter, and
> only if you're given a different question from the current one.
Yeah, there's plenty of ways around it but simply not needing to do it
is always the easy way out :-)


Tim Rowledge, tim@sumeru.stanford.edu, http://sumeru.stanford.edu/tim
Useful random insult:- Wasn't fully debugged before being released.