> I'm working on the pre-merged modern-dispatching branch that Leslie > kindly provided and I've discovered a flaw -- thought I'd discuss it > here first before actually refactoring code. > > First, the new navigation concept is better than the old one. I like the > container abstraction. Things are nicer. > > Problem is, the new design conflates three different concepts: > dispatching, rendering a selector (menu) and rendering selected content > (navigated content).
I have been working only on dispatching. A useful side-effect of this WRT navigation was that we can finally render the body after the menu (without capturing the html of the body first which is a bloody kludge).(*) Yarek happened to work on generic selector items and since this crossed with my changes we decided to lump it together in one branch, similar to what we are doing now. > 1. I need to have the menu rendered separately from the content, and no, > I do not want to use position: absolute in CSS. Who does? I've tried hard to cope with this but by now I'm firmly convinced that taking a natural page element out of the flow is a very bad idea. I have applied the (*) kludge to all my navs since. > Granted, the second issue is more of an inconvenience, than a real > problem, but I think it points to a design issue. > > The interface I think I would like to have is: > > (make-navigation ...) returning a single container with both the menu > and the content -- for simple cases, > > (make-split-navigation ...) returning a list with separate menu and > content widgets, with separate ids. Sounds good. > More fundamentally, I think this is an "inherit vs contain" problem -- > conceptually, navigation should not BE its selected content. It should > BE a dispatcher and possibly BE a selector, but it should KNOW ABOUT and > influence selected content. Yes. > I think fixing this will allow us to untangle the whole > dispatcher/selector/selector-mixin/selector-item/navigation business, > which I think is way too complex right now. I completely agree. The nav system still confuses the hell out of anyone new trying to hack it or use it for more complex purposes. For me the questions are: what will the final design look like, who's going to figure it out and who's going to write it? Leslie -- LinkedIn Profile: http://www.linkedin.com/in/polzer Xing Profile: https://www.xing.com/profile/LeslieP_Polzer Blog: http://blog.viridian-project.de/ --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
