On Wed, Feb 11, 2009 at 5:33 PM, Jan Rychter <[email protected]> wrote:
> Some of those are navigation fixes which will conflict with my branch (I
> ripped out the existing navigation stuff pretty much wholesale...), so
> it's up to the maintainers to decide which way to go.
I'm only fixing what prevents me from getting stuff done and I don't
have the time now to switch to the new navigation model. Many of the
fixes in my branch probably don't apply to the dev branch, but I think
some are useful.
> Disabled items are a good idea and I should probably implement them as
> well.
My reasoning for it is actually a "guide" style navigation where the
user goes through several steps. The user should see all the steps,
but only one at a time should be enabled (or they'll get enabled as
the user goes through them).
> Funny, though -- I just saw your commit 93642076d03c ("modifying menu to
> properly select a tab by default") and remembered implementing the same
> fix a long time ago :-) Later on I switched to selecting by uri-tokens
> (target) which seemed like a more controllable solution.
Yep, ultimately it's selected by uri-tokens anyway, the question is
who does it, the menu itself or whoever calls the menu :)
--~--~---------~--~----~------------~-------~--~----~
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
-~----------~----~----~----~------~----~------~--~---
