Hi >Hi *, > >On Wed, Jan 26, 2005 at 01:46:50PM -0800, Louis Suarez-Potts wrote: >> >> >Cons >> >* a radical departure from what we have now...maybe too radical I don't >> know >> >* how easily can other pages be merged into this framework? >> >> My guess: not easily. Nor would that be desirable for most projects, >> many of which use the left navbar very actively. > >Na, disagree. Many have their additions/replacement in the navbar, many >others have an additional navbar that is used.
yes... but how is that disagreeing with me? Christian, I tend to suspect we actually agree much of the time you think we disagree.... [snip] >No. I don't think so. >There is no reason why projects should not use a navbar, by why should >it be enforced? To have consistency which makes it ultimately easier to navigate. We had a small version of this discussion on [EMAIL PROTECTED] If you recall, I am for the idea of using hu.openoffice.org as a model, provided it can be staticized, for NLC projects. The objection was that we needed a consistent set of elements, otherwise, confusion. >Using css you could create a "sticky" navbar (does not scroll with the >page) or whatever you want. > >I still vote for getting rid of the automatically generated navbar. For Homepage (HP) or all pages? For HP, that is feasible; may also be feasible for user specific pages. For all project pages I say no, at least not at this point. > >ciao >Christian FWIW I asked CollabNet for a staging server so we could test these CSS implementations and am still waiting. best Louis --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
