"Leslie P. Polzer" <[email protected]> writes: >> How about getting rid of the base-uri slot altogether? That way, >> navigation would render relative URLs, code would be simpler, and would >> work better. >> >> The only other use for base-uri is code that redirects to the first pane >> if no default pane was provided. I do not think we can redirect to a >> relative URL, but I don't see a big need for this functionality. And >> perhaps someone can think of a solution not involving base-uri here? > > The current base URI might be useful for more elaborate purposes > (building links, specifically). But let us get rid of BASE-URI > and think of another solution later as needed.
Ok, I finally got around to this. This is not an obvious fix, unfortunately. One thing is that base-uri is unnecessary in my opinion and we should get rid of it. Relative links should be used whenever possible anyway. If anybody has a good use for base-uri (or needs absolute links in navigation widgets), please speak up now. > But what worries me is how the flow-introduced nav will decide > on its children if it's not instructed specifically to do so. That is a more significant issue. > The current code might account for that, of course; I haven't > checked. It does not. I always assumed that actions would not perform major tree modifications and a full tree shakedown would not be required. Now that I think of it, it was an incorrect assumption. There could be many cases when you will need to shake down the tree and determine exactly what the children are all the way down. Here's what I propose (please comment); 1. Get rid of base-uri. 2. Perform a tree shakedown (call update-widget-tree) on both normal requests and AJAX requests. I don't fully understand how the URI could change here, but I assume we can just process the uri-tokens as usual. --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 -~----------~----~----~----~------~----~------~--~---
