> > (2) On receipt of the AJAX answer, if the isearch contents
have
> > changed, then do not apply but discard the AJAX answer (and potentially
> > make a new request).
Afaik, this would be rather hard to do since weblocks doesn't give us
hooks into the Ajax-JS processing [1]
Instead, the dirty objects are marked and collected Lisp-side, the
json hash of {widgetid --mapped--> new-html} is created, and then in
one fell swoop in weblocks.js, their divs are updated with the new
html.
Another, more promising table approach was using the YUI table and
writing a RESTy search function that performed the search and returned
JSON data which YUI knew how to display. Being more JS oriented it was
also easier to do table-size animations and suchlike, iirc. I used the
basic table example from
http://developer.yahoo.com/yui/examples/datatable/dt_autocomplete.html
The following cool code from Leslie lets us selectively exempt
functions from regular AJAX processing (http://paste.lisp.org/+1U15#4)
-- please ignore the crufty hellacious comments if any ;-)
hth,
Nandan
[1] (I've had some use-cases where these would be welcome, but they
were all related to UI-tweaking which can wait).
--~--~---------~--~----~------------~-------~--~----~
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
-~----------~----~----~----~------~----~------~--~---
