My web applications have pages that display many static fields.
I know that poor layout invariably leads to information overload and poor readability.
My question is:
Are there any recommendations or heuristics for placing a screen containing many static fields?
Typically, I would call Bill Scott and Theresa Neil , but I can not find any recommendations on this issue.
Here are some guidelines I tend to follow:
Perhaps there will be a "Details on request . " Ask yourself what data is absolutely and immediately related to the user and group them, hiding other data. You can always provide an “Expand” link or a control that allows the user to view details as desired.
(It's good to see that you are looking at interface design patterns. They are often overlooked!)
HR . , , , , , "web 2.0" ( lol) . , - , .
, , . , , , - .
, , , .
Source: https://habr.com/ru/post/1715335/More articles:call the boulder validator in the MultiActionController ModelAndView method ... maybe? as? - javabit.ly - API Stat Tracking - urlConvert Double to Integer for GetHashCode in Delphi - doublePrinting PRN Files from C # - c #Hi load balanced load server using WCF and MSMQ - c #Is there an automated way to determine the dependencies of shared objects? - linuxКак центрировать изображение переменной ширины в DIV на странице? - htmlIs there a way to format a full python buffer in emacs with a keystroke? - pythonHow do you use a presentation model with Winforms? - design-patternsReading php.ini using zend to extend PHP (and not the PHP language) - cAll Articles