Hi Louis, On Wed, Jan 26, 2005 at 02:18:48PM -0800, Louis Suarez-Potts wrote: > >On Wed, Jan 26, 2005 at 01:46:50PM -0800, Louis Suarez-Potts wrote: > [..] > >> >* 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?
You write "nor would that be desireable" (I think you're talking about removing the navbar) > Christian, I tend to > suspect we actually agree much of the time you think we disagree.... Maybe. > [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. OK, then I propose a different solution: Create the navbar, but with empty content. Let the projects decide what should be placed inside the navbar using their project_tools.html > 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. I am *convinced* that it can be staticized. And I agree that a set of basic options should be available, but have the projects use their translation, their links. Don't provide a "standard" that just wastes space. > >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? Getting rid of the navbar for all projects. Or to be more precise: Getting rid of the contents of that navbar. I'm convinced that projects will use navbars. It is only that the default, enforced navbar doesn't make sense in almost every case. So maybe a compromize: Don't get rid of the navbar, but get rid of the Project Tools > 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. OK for me. But I'm still convinced that the navbar just is accepted, not wanted by the projects. > FWIW I asked CollabNet for a staging server so we could test these CSS > implementations and am still waiting. Could we try the /nonav/ solution as well please? ciao Christian -- NP: Soulfly - Pain --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
