Hi Ian,
On Jun 25, 9:24 pm, Ian Eslick <[email protected]> wrote: > I believe permanent actions are still supported via def-permanent- > action (or something similar). Since the handler executes in the > session context, you can store a reference to the active widget > (assuming only 1 such widget active per session) in the session table. Great! That's exactly what I was looking for. You are correct in assuming that there is only one such widget active per session. > If you want the SVG itself to change in response to a click via a > server side response - you'll either need to run a javascript handler > that interacts with That's what I will do -- I have a simulation of that (without the server reply :)) readily prepared. > it or ship out a new file (or generate a new file) > in your response. Re-shipment is ugly and will lead to flickering/minor realignment issues (at least on opera). I just want to avoid keeping state in two places (and risk getting things out of sync) by only modifying the visual part (SVG) after a server reply indicates that the session data knows what the user did. > I'm not sure this addresses all the issues, but hopefully it's a > helpful scenario to think about. This is very close to a solution I believe. I will see what I come up with tomorrow and post some solution snippet here if I have one. Thanks, Utz --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "weblocks" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [email protected] For more options, visit this group at http://groups.google.com/group/weblocks?hl=en -~----------~----~----~----~------~----~------~--~---
