[Seaside] Dynamically updating the options of a select tag

Julian Fitzell jfitzell at gmail.com
Sat Jun 12 11:44:57 UTC 2010

Well, the callbacks are stored in the RenderContext, which is in the
ActionPhaseContinuation. There's no provided API for getting the
current action phase continuation at the moment, but it would be in
the context stack and you could look it up again from the session
based on the _k key. Maybe we should be stashing it in a
RequestContext property so it is accessible - might be a useful thing
to have around. As a test, you could customize
WASession>>handleFiltered: to do that.

I have no idea how beneficial the optimization would be, off the top of my head.


On Sat, Jun 12, 2010 at 10:17 AM, Jan van de Sandt <jvdsandt at gmail.com> wrote:
> Hello,
> I have three select lists. When I select an item in the first list the
> second list should be updated. And when I select something in the second
> list the third list should be updated.
> I implemented this with jQuery and everything works fine. But I had an idea
> to make everything a bit more efficient by only updating the option tags and
> not the select tag itself on each ajax request. But now I run into the
> problem that the values of the WAValuesCallback are not updated
> automatically. Is there a way that I can get to the callback when processing
> the ajax request so I can update the values? Or should I just forget about
> this optimization.
> Jan
> _______________________________________________
> seaside mailing list
> seaside at lists.squeakfoundation.org
> http://lists.squeakfoundation.org/cgi-bin/mailman/listinfo/seaside

More information about the seaside mailing list