Not sure if you can work this out with your navigation, but a trick you can use to create "fake static / dynamic menus" is to create several different skins for each navigation piece.
For example I have a site with one horizontal menu top main category. I also have a second menu on the left vertical which is 2nd teir. I then have a 3rd navigation menu above my main content pane which acts like a feature's button basically just a horizontal bar which acts like a fancy bread crumb of flash images etc.
My main menu top(H) is -1 scope with recursive=false gives me just my root items. When a user clicks on Link1 it sends them to Link1 page which has a skin of link1 set for it, in this skin I set the scope of my left(V) menu to equal the tab id of Link1 this means my left(V) only shows root or full children (based on recursive setting) for Pages of Link1 if you click on a child of page link1 it has the link1 skin which has the forced scope.
Now if the user clicks on Link2 top(H) menu it sends him to Link2 page and the skin is Link2 for all the children this sets the left(V) scope to the tab id for Link2 nav.
Now for the "3rd" menu similar deal you can use the tabid from the 2nd menu to control the skin which can control the appearance of all parent menus above.
Now this starts to get messy and really un managible beyond 2 layers as your creating a skin for each teir of your navigation. For me it works wonders though I have 6 main categories, and then just one child level under most with just a few exceptions. The bonus to this is I can control how ever previously selected menu appears without having to need any connection between them.
The downside to this though is that is specific to the installation. You can't port the skin across different installations without going back into your xml / ascx files and updating the scope attributes to reflect the new tab ids.
Now if we could tie all the different levels together and select / grab the ones we want and keep a trail through the different ones that would be totally awesome. As it stands that is the one key thing HouseMenu lacks vs snapis's menu with their menu system you have more access to the different teirs in the navigation and better control over what to display and when / how. Overall though I perfer HouseMenu cause its much create off the wall solutions with. Oh and its free and doesn't force me to charge 50 bucks for my skins cause I used it.
|