Jan Rychter <[email protected]> writes: > "Leslie P. Polzer" <[email protected]> writes: >> R. Matthew Emerson wrote: >> >>> A project I'm helping with is running into this problem, too. >>> >>> If anyone has a work-around or unofficial patch that I could use while >>> we wait for a fix to be committed to weblocks-dev, that would be >>> helpful. >> >> Jan, what's your status here? > > Sorry. I'll have a patch out by tomorrow.
Actually, having looked into the problem, I'm looking for feedback on the following points (thoughts): -- a quick fix for the base-uri problem is to redirect after the action (or issue a non-ajax request), this will cause a full request, the tree will be updated and everything will work, -- this kind of tree modification will only work if it doesn't have to modify the URI, so in most cases you will be redirecting or doing a full request anyway, -- if we enable the possibility of swapping in navigation widgets in AJAX actions, we need to do a tree shakedown on every request (including AJAX requests), -- the URI of an AJAX request is not something we can rely on (there is a comment about w3m in make-action-url?), -- so in order to support AJAX swapping of navigation widgets we would have to remember the last "normal" request URI and use that to do the tree shakedown. I'm having second thoughts about whether this is something we want to do. My main point is that there are very few cases where you swap in a navigation widget in an AJAX request (without changing the URI), so I am not sure if we want to build machinery to support that and run a tree shakedown on every AJAX request. Perhaps it is enough to document it and tell everyone to set :ajaxp nil when they are about to modify the navigation hierarchy in the tree? Thoughts? Comments? Am I way off? --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 -~----------~----~----~----~------~----~------~--~---
