On Fri, Mar 20, 2009 at 10:39 PM, Ian Eslick <[email protected]> wrote: > The first is pretty easy, I hope. As we walk the widget tree invoking > navigation functionality, we have a new method that is called on each > widget that can be specialized to extract URL parameters and update > widget state without messing with rendering - essentially a potential > action tied to each widget. That's pretty low level. Would be nice to build some higher level machinery to do it automagically by declaratively specifying that a given slot should be serialized into the URL. Of course this could always be built later by providing a default implementation of the method.
> The second is a little trickier This sounds rather complicated. I prefer to turn off AJAX when a significant update is done to the widget hierarchy. So far it worked pretty well for me, but my applications don't exactly push the boundaries in terms of dynamic UI... --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
