|
From: Chris G. <cm...@do...> - 2003-12-28 03:27:40
|
Mian H Khalil <Has...@hu...> writes: > Neither Lina nor myself felt that we wanted to continue that trend, > which, from a graphic design point of view is not optimal. So to > answer your question, yes it is possible, but I don't foresee it > being done anytime soon. Nevertheless, if we get numerous complaints > on the user-level from this, IE non developmental staff, then we > will reconsider. ipaudit-web is one of those top-left sidebar designs so clicking on screenshots makes the eye retrain with each click. Please don't take this as a suggestion to redesign ipaudit-web. Since we're getting into human feel, a sidebar where the related pages for one section will link to another page with no related pages provides a faux navigation. Eg: http://ipaudit.sourceforge.net/documentation/index.html has related links to how it works... but the http://ipaudit.sourceforge.net/documentation/howItWorks.html isn't related to the man pages. > By tailoring the content to graphic design standards, rather than > development standards, we aim to provide a site that is more easily > navigated by all, including but not limited to developers. If there were 100s of pages of content, dividing upcompartementalization makes sense. I'm in favor of having something meaningful to not use the scroll functionality for the initial page load to make sense. However, scrolling is a very cheap user operation with mousewheels but clicking with the foward/back button forces the user to maintain lots of navigational state. The more I click a mouse, the more likely my hand pains are to flare up. That's a hard thing to think about when designing a web site. Biggest Nit: Isn't the right ipaudit for people to be using the one that's shipped as a part of ipaudit-web? Neither the main page or the ipaudit-web page or downloads page indicate thtat ipaudit is part of ipaudit web and you really only need 1. Cheers, Chris -- Chris Green <cm...@do...> "Yeah, but you're taking the universe out of context." |