Hi Robert! +1 to your suggestion, I'm playing with another site and just found the issue you described :) Thanks for your help! Simo
http://people.apache.org/~simonetripodi/ http://simonetripodi.livejournal.com/ http://twitter.com/simonetripodi http://www.99soft.org/ On Sat, Oct 15, 2011 at 2:32 PM, Robert Scholte <[email protected]> wrote: > > I like the idea. > > > > But we might improve the top-nav a bit. > > Suppose you have a lot of links (or just a small browser) then the top-nav > will claim another row. > > I think we need some sort of fancy horizontal scrolling support here. > > > > -Robert > > ---------------------------------------- >> Date: Sat, 15 Oct 2011 14:17:55 +0200 >> Subject: Re: [skin][fluido] Menu location >> From: [email protected] >> To: [email protected] >> >> Hi Ivan! >> the reason why I started adding menus in 2 places is that while the >> sidebar is fixed in the page, the topbar is always available while >> scrolling the pages; immagine the skin applied to the Apache Commons >> Digester guide[1], once reached the bottom page, users have the >> commodity to avoid scrolling up to open a new guide page. >> >> My proposal is to keep it ATM to experiment and collect feedbacks from >> users too, maybe if we are lucky enough we attract more users to >> express their opinion :) >> WDYT? >> >> Have a nice WE! >> Simo >> >> [1] http://commons.apache.org/digester/guide/binder.html >> >> http://people.apache.org/~simonetripodi/ >> http://simonetripodi.livejournal.com/ >> http://twitter.com/simonetripodi >> http://www.99soft.org/ >> >> >> >> 2011/10/15 Ivan Habunek <[email protected]>: >> > Hi guys. >> > >> > The way it is now in sanbox, the <menu> from site.xml is rendered in the >> > side bar and in the top bar. Additionaly <links> are rendered in the right >> > part of the top bar. >> > >> > I think there's no reason to have <menu> rendered in two places. I can see >> > several options here: >> > >> > 1. Render the <links> in the top bar, and <menu> in the side bar. >> > >> > The problem is that currently, <item> nodes in <links> cannot have >> > children, >> > like they can in <menu>. See difference between LinkItem and MenuItem in >> > the >> > XSD [1]. >> > >> > This means that the links in the top bar cannot have drop-down lists like >> > it >> > is implemented now. For me this is not a big problem, but it does limit the >> > available functionality offered by bootstrap. >> > >> > 2. Render both the <menu> and <links> in top bar, remove the sidebar. >> > >> > This is the way it is now, but minus the sidebar. Personally, i don't want >> > to remove the sidebar, it is much more appropreate for larger menus. >> > >> > What do you think? Should we go with 1.? Any other ideas? >> > >> > Regards, >> > Ivan >> > >> > [1] http://maven.apache.org/xsd/decoration-1.1.0.xsd >> > >> > --------------------------------------------------------------------- >> > To unsubscribe, e-mail: [email protected] >> > For additional commands, e-mail: [email protected] >> > >> > >> >> --------------------------------------------------------------------- >> To unsubscribe, e-mail: [email protected] >> For additional commands, e-mail: [email protected] >> > --------------------------------------------------------------------- > To unsubscribe, e-mail: [email protected] > For additional commands, e-mail: [email protected] > > --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
