On Fri, Feb 13, 2009 at 10:09 AM, Ian Eslick <[email protected]> wrote: > Is there a cheap ajax way to suspend click > interpretation during ajax updates until we get a response? One way to do it is give each ajax link a specific css class (like 'ajax') and go through them on ajax calls and set them to simple text styled as links. When the ajax completes (or after a time out) one could go through the links again and reenable them. Shouldn't be too difficult to do with JS (I don't have the syntax in my mind, but seems like only a few lines of code).
Another, probably cheaper way, would be to intercept mouseClick events and set propagate to false for the time of the ajax call. It should be possible and should only take a couple of lines of JS (and an hour or so to figure out what these lines should be). > 1) Processing URL parameters for friendly URLs Do you mean processing tokens? I use `uri-tokens-start-with' function. If you mean the query string, I use keyword args on actions (i.e. (lambda (&key query-arg-1 query-arg-2 &allow-other-keys) ...)) and let weblocks do the grunt work. Occassionally I also look at these during rendering, but in this case I drop to hunchentoot's functions. It should be easy to map widget slots to query strings and have them automatically updated by weblocks, but I haven't done that yet and I'm not sure if anyone else has either (it'd be great if that were in place). --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
