Bill Moseley wrote:
At 12:57 AM 01/13/02 +0800, Stas Bekman wrote:
Well, as you can imagine it's not going to work. It's easy to implement, but it won't be user friendly, because some subsections of the menu will have many items with very long titles.Or does someone else want to do the expanding NavBar?
Why not use a map (hash) in each directory's config file?
This should work ok for first and second level menus, and in some cases would be a good way to "translate" a title that doesn't make much sense out of context or is too wordy into a more concise menu item.
What I'm trying to say is that we don't have a technical problem. It's not an issue of how the configuration file is constructed. It's an issue of most of the titles being long and not fitting into the menu. I doubt you can shrink them, if you could they won't be long in first place.
Before we go any further and waste time trying to build an expandable menu. Go to any of the docs dirs and try to construct an expanded menu that will fit into a left "narrow"(!) column.
If we could apply our content to an expandable menu that would be the perfect solution, but as you realize we cannot. The only way we could do that if we have taken the whole width of the page's top for this purpose, which can be a good solution.
So, what's your opinion of http://www.w3schools.com/xml/default.asp?
That's comparing oranges with apple, no?
It's almost a flat site with only 2 levels of nesting and titles of a single word, which is not what we have.
_____________________________________________________________________ Stas Bekman JAm_pH -- Just Another mod_perl Hacker http://stason.org/ mod_perl Guide http://perl.apache.org/guide mailto:[EMAIL PROTECTED] http://ticketmaster.com http://apacheweek.com http://singlesheaven.com http://perl.apache.org http://perlmonth.com/
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
