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 -~----------~----~----~----~------~----~------~--~---
