Nav fix
Leslie P. Polzer
If no one has volunteered by tomorrow to get this (really) done within
the next few days I will fix it as I see fit.
Leslie P. Polzer
http://bitbucket.org/S11001001/weblocks-dev/changeset/2a249589f4c0/
Selector now has better handling of default panes as well:
http://bitbucket.org/S11001001/weblocks-dev/changeset/ef8193c197bd/
http://bitbucket.org/S11001001/weblocks-dev/changeset/d14a261e0a43/
These changesets and 0bd9eee79c9d would benefit from test cases.
Step in as you like, writing test cases provides an excellent learning
opportunity.
Next release due in a few days, so please also help find remaining
bugs.
Leslie
Jan Rychter
From what I remember, the result of our discussion was that this is
"notabug" -- an update that touches the structure of selectors within
the tree requires an URL change anyway, so we might as well redirect.
--J.
Leslie P. Polzer
Jan Rychter wrote:
> From what I remember, the result of our discussion was that this is
> "notabug" -- an update that touches the structure of selectors within
> the tree requires an URL change anyway, so we might as well redirect.
The discussion did not have a definite result. In fact I've been
waiting for your answer...
http://groups.google.com/group/weblocks/browse_thread/thread/51fe560b0a7cc36a/1c5fee63f2c45bee
Jan Rychter
Oh -- I'm sorry, then. I thought the case was closed and didn't even
have this on my TODO anymore.
--J.
Leslie P. Polzer
Jan Rychter wrote:
> Oh -- I'm sorry, then. I thought the case was closed and didn't even
> have this on my TODO anymore.
Anyway, I hope my solution satisfies.
The redirect would have been another option but at the expense of
a smooth AJAX experience.