In part-I, I wrote about how dialog boxes can make your application look infested with bugs. In order to solve this, as a designer your aim should be to minimize dialog boxes as much as you can and if a dialog box is really a need then think about making it a modeless dialog box.
Let us assume you have a web application where you want to create a web page to display a list of items. Consider its design; you need a list page and an
My suggestion is let’s try to be innovative and let’s design for the user and not for the application.
Now regarding the above dialog issue, we can add input fields, which we were displaying in the dialog, at the top of the list page and provide
----------------------------------------------------------------
Headers--> First Name Last Name Email Address
----------------------------------------------------------------
Inputs--> Field1 Field2 Field3
List-->
For editing you can either provider edit image/button in each row or a EDIT HTML link.
In the list above we achieved the same functionality as of a dialog box and much more. Much more? Well using this approach you can easily provide copy row functionality also. Consider the list below; a user can enter values in Field1, Field2 and Field3 for First Name, Last Name and Email Address and press
Hope this helps. I will be back soon with more user interface design issues.
Monday, October 24, 2005
Dialog Box, a bad user interface design element-Part 2( Alternative to a dialog)
Subscribe to:
Post Comments (Atom)
No comments:
Post a Comment