> I need to expose the state of some widgets via a query string (for > example, for dataseqs it would be sorting and paging information).
You want to connect with Ian to avoid duplicating work. > In src/widgets/widget/widget-mop.lisp, add a new > expose-via-query-string-p slot to widget-slot-definition-mixin. This > lets the programmer declaratively state which widget slots should > expose their state to the URI. That's a good start. > Because a single page may contain > multiple widgets with the same slot names, when exposed to the URI the > slots may be prepended by the widget's id. If the ID is an ephemeral symbol then it will not be an URL that can be shared. > Also, because the programmer may want to turn the behavior off for some > widgets, it's > probably a good idea to add expose-via-query-string-p > slot to widget class itself, and to look at it before serializing widget > slots to the query string. Yes, a useful extension. Perhaps add a global switch, too. > When I render a page that has color-chooser in it, I get > /foo/bar?color=red. Obviously, if the user types in > /foo/bar?color=blue, weblocks will automatically update the slot in > the color-chooser. How is this going to mix with AJAX updates? JavaScript still isn't allowed to change the query string in place. > Thoughts? Will this work with the new additions/modifications to weblocks? I don't think there will be any incompatibilites. I say this lightly, though. > On a different note, could someone take a little time to write a > summary of the new additions/modifications to weblocks? I don't want > my branch to hopelessly diverge from offical weblocks, and maintaining > everything in sync is hard (what will I have to change in my app and > how much work will it involve?). Gladly, but you need to be a bit more specific. Are you talking about upcoming merges, or a certain window that has already gone by...? Leslie --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
