Ian Eslick <[email protected]> writes: > I think that's the idea; let's not overcommit until we see how people > use it. Any other comments or feedback? I think some basic support > could be provided fairly quickly with some careful surgery on the walk- > widget method so we can experiment. A sprint if you will...
Sounds good so far -- IMHO update-widget-tree (right after the update-children call) is the place to do it, but someone needs to design an interface/protocol. By that I mean something similar to the update-children/get-widget-for-tokens/update-dependents trio used for handling URI tokens and selection within the tree. There is also the question of whether parameters can modify the tree structure. I would suggest avoiding this. --J. > On Mar 21, 2009, at 1:50 PM, Jan Rychter wrote: > >> >> Ian Eslick <[email protected]> writes: >> [...] >>> 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. Perhaps this is already effectively >>> there? Individual users can decide how to create hard links that >>> generate these parameters. >> >> Do we leave the naming of the parameters up to application developers? >> E.g. it is up to each widget to decide what it wants to extract? >> >> I suppose so, because if we try to force any structure we basically >> end >> up with a duplicate of the uri-token selector scheme, only for URL >> parameters... >> >> --J. >> >> > > > > --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
