> Well, the second part is the archives. Of course, you know that. What's the
> solution, though? We have a page that describes all the mailing lists, & we
> have links to the list archives. Do we take the archive links out of the
> navbar? I think having them there just might make some people look there
> before mailing the list for help. We could put the mailing list page link in
> the mailing list section of the navbar... but then what labels would we give
> things so that people know that the first is a page describing all the
> lists, while the other links are just links to archives?
I say drop the mailing list archives from the short top navbar, but keep them
for the long, side navbar.
> I'm afraid I have no idea why. I thought it might be the "nowrap" in the
> <td>'s, but they make words not wrap *within* their cells. But now that I
> think of it, I can't imagine that you could wrap tables: allowing one row to
> wrap would screw up the tabularity. I *guess* you could do it by making
> "Home","Devvies","Download" etc. all be in one <td> instead of each one
> being a separate <td>. Problems with that? Well, it means the items in the
> three rows of the (top) navbar won't line up nicely. (Yes, you could make
> Home, Devvies, etc., into a *table* inside the one <td>, but that would be
> more complicated.) But I don't really care how we do this.
The reason is that the second row of the table does not have enough
cells. We need to put in empty cells and insert a non-breaking space
inside them (because of Netscape HML rendering bugs).
> > Is it possible to turn the options (titles, on top/bottom) into
> > checkboxes? It would be fancy.
>
> Asger? I don't even know how to do it in HTML, so I certainly don't know how
> to do it in php3.
Of course that is possible, but they would behave a little strange:
When you click, the page is reloaded. Hardly the behaviour you expect
from a check-box.
However, we could find a better look that suggests that it is a kind of
check-box. When I find the time, I'll do something about it.
> Is the navbar getting too big? We've got 9 things in the navbar, lgt would
> make 10, mirrors 11. Do we want to perhaps break things down into About,
> Download, Main? Then have a separate submenu for each, s.t. the navbar shows
> the main menu, the submenu that makes sense in that context, plus the
> mailing list archives & configuration thing? Or is that too complicated.
I don't think the side navbar is too big.
The top, short one is too big, and we should do something.
I don't like sub-menus on web-pages, because that makes it difficult
to find things.
And we will never be able to keep a site-map up to date,
so let's not introduce such a thing. I say, let's keep the long side
navbar, but nuke the non-essential items from the top short one.
Did I implement support for this differentiation in the php engine yet?
If not, I guess Amir could do it ;-)
Greets,
Asger
