Content deleted Content added
adding links to references using Google Scholar |
GreenC bot (talk | contribs) Rescued 1 archive link; reformat 1 link. Wayback Medic 2.5 |
||
Line 42:
An [[interaction task]] is "the unit of an entry of information by the user",<ref name="foley"/> such as entering a piece of text, issuing a command, or specifying a 2D position. A similar concept is that of [[___domain object]], which is a piece of application data that can be manipulated by the user.<ref name="mbl">M. Beaudouin-Lafon (2000) [https://kedwards.com/classes/AY2016/cs4470_fall/readings/instrumental-interaction.pdf Instrumental interaction: an interaction model for designing post-WIMP user interfaces]. In Proceedings of the SIGCHI Conference on Human Factors in Computing Systems.</ref>
Interaction techniques are the glue between physical I/O devices and interaction tasks or ___domain objects.<ref name="mbl"/><ref name="dragicevic">P. Dragicevic and J-D Fekete (2004) [http://www.academia.edu/download/31801023/ICon-AVI04.pdf The Input Configurator toolkit: towards high input adaptability in interactive applications]{{dead link|date=July 2022|bot=medic}}{{cbignore|bot=medic}}. In Proceedings of the Working Conference on Advanced Visual interfaces.</ref> Different types of interaction techniques can be used to map a specific device to a specific ___domain object. For example, different [[Handwriting recognition|gesture alphabets]] exist for [[Pen computing|pen-based]] text input.
In general, the less compatible the device is with the ___domain object, the more complex the interaction technique.<ref name="buxton">W. Buxton (1986) [http://www.billbuxton.com/eye.html There's More to Interaction than Meets the Eye: Some Issues in Manual Input]. In Norman, D. A. and Draper, S. W. (Eds.), User Centered System Design:
| |||