Bureaucrats, emailconfirmed
1,221
edits
IFD:Course Interaction Design (view source)
Revision as of 09:12, 18 November 2010
, 18 November 2010→Standards and Consistency
| Line 336: | Line 336: | ||
* The cockpit of a car - we could use a joystick for steering and push-buttons for setting the direction indicators but we don't in order to enable everybody to drive any car without relearning driving. | * The cockpit of a car - we could use a joystick for steering and push-buttons for setting the direction indicators but we don't in order to enable everybody to drive any car without relearning driving. | ||
* There is just a very rough connection of Application windows to windows in the real world, but we learned what | * There is just a very rough connection of Application windows to windows in the real world, but we learned what it is. | ||
* A right-click triggers a context menu | * A right-click triggers a context menu | ||
* Files are organized in Folders | * Files are organized in Folders, though "boxes" or any other thing that contains something is equally fine. | ||
[[File:DialogBox-standards_openSource.png|thumb|300px|Some Standards you can see here:A Bar on top you can drag the window with; A cross in the corner that closes the window; Buttons with descriptive Text triggering functions - and the whole dialog is a standard in itself because it always appears when one closes an application without prior saving]] | [[File:DialogBox-standards_openSource.png|thumb|300px|Some Standards you can see here:A Bar on top you can drag the window with; A cross in the corner that closes the window; Buttons with descriptive Text triggering functions - and the whole dialog is a standard in itself because it always appears when one closes an application without prior saving]] | ||
| Line 354: | Line 354: | ||
* ...and you tested it to ensure that it works like intended. | * ...and you tested it to ensure that it works like intended. | ||
This is often done for a good reason in applications like 3D Modelling Environments. These applications often have a steep learning curve, are very powerful, complex and deal with something (3D) that is not common in the most applications (mostly concerned with 2D stuff. | This is often done for a good reason in applications like 3D Modelling Environments. These applications often have a steep learning curve, are very powerful, complex and deal with something (3D) that is not common in the most applications (mostly concerned with 2D stuff). | ||
"Standards" are concerned with having not to relearn things with an perspective to different applications and systems. We don't want that the user needs to relearn while using a single product as well. This is often refereed to as "consistency". This mean in your application you use the same conventions all over the place. If you e.g. enable changing the color of items via the contextmenu, this should be possible with all times. If you enable to drag and drop items drag-and drop should work application wide. Doing so means that the user just has to learn that your application allows this and that way of interaction. If the interaction is inconsistent on the other hand, users would need to learn in which places something works. | "Standards" are concerned with having not to relearn things with an perspective to different applications and systems. We don't want that the user needs to relearn while using a single product as well. This is often refereed to as "consistency". This mean in your application you use the same conventions all over the place. If you e.g. enable changing the color of items via the contextmenu, this should be possible with all times. If you enable to drag and drop items drag-and drop should work application wide. Doing so means that the user just has to learn that your application allows this and that way of interaction. If the interaction is inconsistent on the other hand, users would need to learn in which places something works. | ||