Five Interaction Styles - Revision history

Simpsoa: /* Menus */

2009-11-23T20:49:16Z

Menus

← Older revision		Revision as of 20:49, 23 November 2009
Line 20:		Line 20:

	== Menus ==		== Menus ==
-	[[Image:menus1.gif\|thumb\|~~300px~~\|right\|Example of a typical menu in Windows XP]]	+	[[Image:menus1.gif\|thumb\|100px\|right\|Example of a typical menu in Windows XP]]
-	[[Image:menus2.gif\|thumb\|~~300px~~\|right\|Microsoft Office's "ribbon" UI, an example of tabbed toolbars]]	+	[[Image:menus2.gif\|thumb\|100px\|right\|Microsoft Office's "ribbon" UI, an example of tabbed toolbars]]

	Menus provide a way to visually organise a very large set of actions. Menus are nearly ubiquitous in modern applications, with the most standard format being the "File/Edit" style strip located across the top of windows (such as in Microsoft Windows) or the user's workspace (such as in [[Multiple Document Interfaces]], or in Mac OS X). Menus do not have any obvious physical metaphor, and rely on users being able to tell the difference between an action, and a category which can be expanded into a child set of actions and/or further categories. Menus can also change depending on context, from enabling or disabling individual items depending on the program's state, to using "tabbed toolbars" to flip between item collections.		Menus provide a way to visually organise a very large set of actions. Menus are nearly ubiquitous in modern applications, with the most standard format being the "File/Edit" style strip located across the top of windows (such as in Microsoft Windows) or the user's workspace (such as in [[Multiple Document Interfaces]], or in Mac OS X). Menus do not have any obvious physical metaphor, and rely on users being able to tell the difference between an action, and a category which can be expanded into a child set of actions and/or further categories. Menus can also change depending on context, from enabling or disabling individual items depending on the program's state, to using "tabbed toolbars" to flip between item collections.

Simpsoa at 20:47, 23 November 2009

2009-11-23T20:47:15Z

← Older revision		Revision as of 20:47, 23 November 2009
Line 97:		Line 97:
	# Byron Long, "Natural Language as an Interaction Style", Retrieved on November 21st, 2009 from http://www.dgp.toronto.edu/people/byron/papers/nli.html		# Byron Long, "Natural Language as an Interaction Style", Retrieved on November 21st, 2009 from http://www.dgp.toronto.edu/people/byron/papers/nli.html
	# Bill Buxton, "The "Natural" Language of Interaction", Retrieved on November 21st, 2009 from http://www.billbuxton.com/natural.html		# Bill Buxton, "The "Natural" Language of Interaction", Retrieved on November 21st, 2009 from http://www.billbuxton.com/natural.html
		+	# Microsoft Office Online, "Use the Ribbon - Help and How-to", Retrieved on November 23rd, 2009 from http://office.microsoft.com/en-us/help/HA100898951033.aspx

	--[[User:Shensw\|Shensw]] 22:55, 20 November 2009 (EST)		--[[User:Shensw\|Shensw]] 22:55, 20 November 2009 (EST)
Line 103:		Line 104:

	--[[User:Frostd\|Frostd]] 00:58, 22 November 2009 (EST)		--[[User:Frostd\|Frostd]] 00:58, 22 November 2009 (EST)
		+
		+	--[[User:Simpsoa\|Simpsoa]] 15:45, 23 November 2009 (EST)

Simpsoa: /* Menus */

2009-11-23T20:44:18Z

Menus

← Older revision		Revision as of 20:44, 23 November 2009
Line 21:		Line 21:
	== Menus ==		== Menus ==
	[[Image:menus1.gif\|thumb\|300px\|right\|Example of a typical menu in Windows XP]]		[[Image:menus1.gif\|thumb\|300px\|right\|Example of a typical menu in Windows XP]]
-	[[Image:menus2.gif\|thumb\|300px\|right\|Microsoft's ~~new~~ "ribbon" ~~menu~~]]	+	[[Image:menus2.gif\|thumb\|300px\|right\|Microsoft Office's "ribbon" UI, an example of tabbed toolbars]]

-	Menus provide a way to visually organise a very large set of actions. Menus are nearly ubiquitous in modern applications, with the most standard format being the "File/Edit" strip located across the top of windows (such as in Microsoft Windows) or the user's workspace (such as in Multiple Document Interfaces or in Mac OS X).	+	Menus provide a way to visually organise a very large set of actions. Menus are nearly ubiquitous in modern applications, with the most standard format being the "File/Edit" style strip located across the top of windows (such as in Microsoft Windows) or the user's workspace (such as in [[Multiple Document Interfaces]], or in Mac OS X). Menus do not have any obvious physical metaphor, and rely on users being able to tell the difference between an action, and a category which can be expanded into a child set of actions and/or further categories. Menus can also change depending on context, from enabling or disabling individual items depending on the program's state, to using "tabbed toolbars" to flip between item collections.

	=== + Advantages ===		=== + Advantages ===
	* Accessible to novice and intermittent users		* Accessible to novice and intermittent users
-	* Allows for a very large ~~pallette~~ of structured commands which can be easily "explored"	+	* Allows for a very large palette of structured commands which can be easily "explored"
	* Facilitates Multiple Document Interfaces well		* Facilitates Multiple Document Interfaces well
	* Does not rely on parsing input		* Does not rely on parsing input

Frostd at 20:43, 23 November 2009

2009-11-23T20:43:28Z

← Older revision		Revision as of 20:43, 23 November 2009
Line 97:		Line 97:
	# Byron Long, "Natural Language as an Interaction Style", Retrieved on November 21st, 2009 from http://www.dgp.toronto.edu/people/byron/papers/nli.html		# Byron Long, "Natural Language as an Interaction Style", Retrieved on November 21st, 2009 from http://www.dgp.toronto.edu/people/byron/papers/nli.html
	# Bill Buxton, "The "Natural" Language of Interaction", Retrieved on November 21st, 2009 from http://www.billbuxton.com/natural.html		# Bill Buxton, "The "Natural" Language of Interaction", Retrieved on November 21st, 2009 from http://www.billbuxton.com/natural.html
-
-	~~= External links =~~

	--[[User:Shensw\|Shensw]] 22:55, 20 November 2009 (EST)		--[[User:Shensw\|Shensw]] 22:55, 20 November 2009 (EST)

Frostd: Added Visual representation picture

2009-11-23T20:41:09Z

Added Visual representation picture

← Older revision		Revision as of 20:41, 23 November 2009
Line 4:		Line 4:

	== Visual representation ==		== Visual representation ==
		+	[[Image:DirectManipulation.jpg\|thumb\|300px\|right\|Simple example of file/folder metaphor in Windows Vista]]

	Visual representation (also known as [[Direct Manipulation]]) features a natural representation of task [http://www.cas.mcmaster.ca/wiki/index.php/The_Object-Action_%28or_visa-versa%29_model_and_its_applications objects and actions]. This helps present the process as actually performing a task itself directly even though it is being doing through an intermediary like a computer. The visual representation usually takes the form of a metaphor related to the actual task being performed. In this way well designed visual representation systems tend to make the interaction enjoyable for the users, which is excellent for novice users or complex tasks that can lead to anxiety.		Visual representation (also known as [[Direct Manipulation]]) features a natural representation of task [http://www.cas.mcmaster.ca/wiki/index.php/The_Object-Action_%28or_visa-versa%29_model_and_its_applications objects and actions]. This helps present the process as actually performing a task itself directly even though it is being doing through an intermediary like a computer. The visual representation usually takes the form of a metaphor related to the actual task being performed. In this way well designed visual representation systems tend to make the interaction enjoyable for the users, which is excellent for novice users or complex tasks that can lead to anxiety.

Simpsoa: /* Menus */

2009-11-23T20:32:45Z

Menus

← Older revision		Revision as of 20:32, 23 November 2009
Line 19:		Line 19:

	== Menus ==		== Menus ==
		+	[[Image:menus1.gif\|thumb\|300px\|right\|Example of a typical menu in Windows XP]]
		+	[[Image:menus2.gif\|thumb\|300px\|right\|Microsoft's new "ribbon" menu]]
		+
		+	Menus provide a way to visually organise a very large set of actions. Menus are nearly ubiquitous in modern applications, with the most standard format being the "File/Edit" strip located across the top of windows (such as in Microsoft Windows) or the user's workspace (such as in Multiple Document Interfaces or in Mac OS X).
		+
		+	=== + Advantages ===
		+	* Accessible to novice and intermittent users
		+	* Allows for a very large pallette of structured commands which can be easily "explored"
		+	* Facilitates Multiple Document Interfaces well
		+	* Does not rely on parsing input
		+
		+	=== - Disadvantages ===
		+	* Can bury useful features under complex hierarchies
		+	* Number of items limited by screen resolution
		+	* Convention restricts how menu items are categorised

	== Fill-In-The-Blanks ==		== Fill-In-The-Blanks ==

Collim: /* Command Line */

2009-11-23T20:13:12Z

Command Line

← Older revision		Revision as of 20:13, 23 November 2009
Line 39:		Line 39:
	[[Image:Commandline.png\|thumb\|300px\|right\|Ubuntu command line showing basic commands]]		[[Image:Commandline.png\|thumb\|300px\|right\|Ubuntu command line showing basic commands]]

-	Command line is the earliest used interaction style and is still seen predominantly in Unix operating systems though still usable to varying degrees on Windows and OSX. This style is mainly used by expert users by typing into a prompt that allows them to quickly execute commands. Unfortunately command line places a considerable burden on the user to learn and recall commands from memory. It is often the case that commands take parameters as well and most of the added benefits (mainly in the way of efficiency) come from using them. This leads to an unfriendly environment for both novice and intermediate users that may attempt to use this style. The large overhead in learning commands and minimal help for the user leaves this style almost exclusively in the domain of the expert user.	+	Command line is the earliest used interaction style and is still seen predominantly in Unix operating systems though still usable to varying degrees on Windows and OSX. This style is mainly used by expert users by typing into a prompt that allows them to quickly execute commands. Unfortunately command line places a considerable burden on the user to learn and recall commands from memory. It is often the case that commands take parameters as well and most of the added benefits (mainly in the way of efficiency) come from using them. This leads to an unfriendly environment for both novice and intermediate users that may attempt to use this style. The large overhead in learning commands and minimal help for the user leaves this style almost exclusively in the domain of the expert user.<sup>[1]</sup>

	=== + Advantages ===		=== + Advantages ===

Collim: /* Fill-In-The-Blanks */

2009-11-23T20:12:43Z

Fill-In-The-Blanks

← Older revision		Revision as of 20:12, 23 November 2009
Line 23:		Line 23:
	[[Image:formfillin1.gif\|thumb\|300px\|right\|Classic Fill-In-The-Blanks]]		[[Image:formfillin1.gif\|thumb\|300px\|right\|Classic Fill-In-The-Blanks]]
	[[Image:formfillin2.gif\|thumb\|300px\|right\|Modern-day Fill-In-The-Blanks]]		[[Image:formfillin2.gif\|thumb\|300px\|right\|Modern-day Fill-In-The-Blanks]]
-	The Fill-In-The-Blanks interaction style (also known as "Form Fill-in") is best suited to data input, which was aimed at a different set of users than command language, specially non-experts users. Originally Fill-In-The-Blanks is to arrange one or more fields in the form of a prose sentence or phrase, with the fields as "blanks" to be filled in by the user. The TAB-key was designed and is still being used to switch between the fields and ENTER to submit the form. Therefore a pointing device (such as a mouse) was not really needed at that time. However it's very common to mix forms with other interaction styles in software design, such as drop down menus, check boxes etc. The spreadsheet is a variation on the Form Fill-in interaction style. Even today, there are quite a few computers are still purely forms-based in the industry, like cash registers, financial systems, stock control systems, and so on. The main reason is because the Fill-In-The-Blanks interface is especially useful for routine, clerical work or those tasks require a great amount of data entry.	+	The Fill-In-The-Blanks interaction style (also known as "Form Fill-in") is best suited to data input, which was aimed at a different set of users than command language, specially non-experts users. Originally Fill-In-The-Blanks is to arrange one or more fields in the form of a prose sentence or phrase, with the fields as "blanks" to be filled in by the user. The TAB-key was designed and is still being used to switch between the fields and ENTER to submit the form. Therefore a pointing device (such as a mouse) was not really needed at that time. However it's very common to mix forms with other interaction styles in software design, such as drop down menus, check boxes etc. The spreadsheet is a variation on the Form Fill-in interaction style. Even today, there are quite a few computers are still purely forms-based in the industry, like cash registers, financial systems, stock control systems, and so on. The main reason is because the Fill-In-The-Blanks interface is especially useful for routine, clerical work or those tasks require a great amount of data entry.<sup>[1]</sup>

	=== + Advantages ===		=== + Advantages ===

Frostd at 17:36, 23 November 2009

2009-11-23T17:36:26Z

← Older revision		Revision as of 17:36, 23 November 2009
Line 1:		Line 1:
-	The '''Five Interaction Styles'''	+	The '''Five Interaction Styles''' originally presented by Ben Shneiderman in 1983 represent the five basic ways that humans interact with a computer interface. Each interaction style effects the overall efficiency and usability of the computer system, but that is not to say there are good or bad interaction styles. The styles all have benefits and trade offs when dealing with certain types of users and it is often in an interface designers best interest to use a combination of styles instead of anyone one style alone.

	= Shneiderman's Five Interaction Styles =		= Shneiderman's Five Interaction Styles =

	== Visual representation ==		== Visual representation ==
		+
		+	Visual representation (also known as [[Direct Manipulation]]) features a natural representation of task [http://www.cas.mcmaster.ca/wiki/index.php/The_Object-Action_%28or_visa-versa%29_model_and_its_applications objects and actions]. This helps present the process as actually performing a task itself directly even though it is being doing through an intermediary like a computer. The visual representation usually takes the form of a metaphor related to the actual task being performed. In this way well designed visual representation systems tend to make the interaction enjoyable for the users, which is excellent for novice users or complex tasks that can lead to anxiety.
		+
		+	=== + Advantages ===
		+	* Visual presentation of task concepts
		+	* Allows easy learning
		+	* Encourages exploration
		+	* Users can immediately see if their actions are furthering their goals
		+	* Users gain confidence because they feel in control and can predict system responses
		+
		+	=== - Disadvantages ===
		+	* Can be hard to implement
		+	* Requires graphics display/pointing devices

	== Menus ==		== Menus ==
Line 54:		Line 67:

	= See also =		= See also =
		+
		+	* [[Motivations for the Studies of HCI]]
		+	* [[Contexts for HCI]]
		+	* [[Process for User-centered Development]]
		+	* [[Social issues influencing HCI design and use]]
		+	* [[HCI - Accommodating human diversity]]
		+	* [[User Interface Standards]]
		+	* [[The Object-Action (or visa-versa) model and its applications]]
		+	* [[Direct Manipulation]]

	= References =		= References =

Frostd at 22:25, 22 November 2009

2009-11-22T22:25:47Z

← Older revision		Revision as of 22:25, 22 November 2009
Line 24:		Line 24:

	== Command Line ==		== Command Line ==
		+	[[Image:Commandline.png\|thumb\|300px\|right\|Ubuntu command line showing basic commands]]

	Command line is the earliest used interaction style and is still seen predominantly in Unix operating systems though still usable to varying degrees on Windows and OSX. This style is mainly used by expert users by typing into a prompt that allows them to quickly execute commands. Unfortunately command line places a considerable burden on the user to learn and recall commands from memory. It is often the case that commands take parameters as well and most of the added benefits (mainly in the way of efficiency) come from using them. This leads to an unfriendly environment for both novice and intermediate users that may attempt to use this style. The large overhead in learning commands and minimal help for the user leaves this style almost exclusively in the domain of the expert user.		Command line is the earliest used interaction style and is still seen predominantly in Unix operating systems though still usable to varying degrees on Windows and OSX. This style is mainly used by expert users by typing into a prompt that allows them to quickly execute commands. Unfortunately command line places a considerable burden on the user to learn and recall commands from memory. It is often the case that commands take parameters as well and most of the added benefits (mainly in the way of efficiency) come from using them. This leads to an unfriendly environment for both novice and intermediate users that may attempt to use this style. The large overhead in learning commands and minimal help for the user leaves this style almost exclusively in the domain of the expert user.