SlideShare verwendet Cookies, um die Funktionalität und Leistungsfähigkeit der Webseite zu verbessern und Ihnen relevante Werbung bereitzustellen. Wenn Sie diese Webseite weiter besuchen, erklären Sie sich mit der Verwendung von Cookies auf dieser Seite einverstanden. Lesen Sie bitte unsere Nutzervereinbarung und die Datenschutzrichtlinie.
SlideShare verwendet Cookies, um die Funktionalität und Leistungsfähigkeit der Webseite zu verbessern und Ihnen relevante Werbung bereitzustellen. Wenn Sie diese Webseite weiter besuchen, erklären Sie sich mit der Verwendung von Cookies auf dieser Seite einverstanden. Lesen Sie bitte unsere unsere Datenschutzrichtlinie und die Nutzervereinbarung.
For a long time, I’ve been a fan of the “liquid layouts,” which are UIs that expand and shrinkdepending on the user’s devices capabilities. I still advocate these layouts. That said, I learned tolimit the amount of horizontal width to consume. Anything past a certain width (about 1,000pixels) is too big. At more than 1,000 pixels or so, the page is so big that the user can’t see it alleven with peripheral vision, and has to move their eyes all over the place. And if they try readingwide chunks of text, they easily lose their place on the page as they scan.So yes, you should use a liquid layout, but restrict the overall size so that it does not consume100% of the horizontal real estate on a large monitor.5: Don’t collapse things, except in rare occasionsAs Web apps look more like desktop apps, it has become stylish to make portions of the screencollapse and expand — and this technique does have its place. For example, it is a good idea inFAQs, as long as it is done in a way that search engines can see the text and index it. At the sametime, when you hide important (or even semi-important) UI elements with a small arrow icon toallow expansion, most people will overlook it.Remember that 1,000 pixel guideline? That’s a good place to use some of that extra space, as longas the usage is narrow. Keep your main area limited to around 1,000 pixels and make a small (150pixels wide) sidebar tacked onto the side to provide space for UI elements that you would betempted to make a collapsible area. Incidentally, this applies to menus as well; users really dislikethe dropdown navigation menus that have become so popular. The dropdown navigation menusare difficult to use, and for people without a mouse (mobile users, disabled users) the menus arevirtually impossible to use.Recommend Office .NET/Silverlight Component:Spire.XLS for .NET and SilverlightSpire.Office for .NET and SilverlightSpire.Doc for .NET and SilverlightSpire.PDF for .NETSpire.DataExport for .NET