| http://dbpedia.org/ontology/abstract
|
A human-to-computer user interface is said … A human-to-computer user interface is said to be "reactive" if it has the following characteristics: 1.
* The user is immediately aware of the effect of each "gesture". Gestures can be keystrokes, mouse clicks, menu selections, or more esoteric inputs. 2.
* The user is always aware of the state of his/her data. Did I just save those changes? Did I just overwrite my backup by mistake? No data is hidden. In a figure-drawing program, the user can tell whether a line segment is composed of smaller segments. 3.
* The user always knows how to get help. Help may be context-sensitive or modal, but it is substantial. A program with a built-in help browser is not reactive if its content is just a collection of screen shots or menu item labels with no real explanation of what they do. Reactivity was a major goal in the early user interface research at MIT and Xerox PARC.A computer program which was not reactive would not be considered user friendly no matter how elaborate its presentation. Early word-processing programs whose on-screen representations look nothing like their printer output could be reactive. The common example was WordStar on CP/M. On-screen, it looked like a markup language in a character cell display, but it had deep built-in help which was always available from an on-screen menu bar, and the effect of each keystroke was obvious.
* v
* t
* eeach keystroke was obvious.
* v
* t
* e
|
| http://dbpedia.org/ontology/wikiPageID
|
7138096
|
| http://dbpedia.org/ontology/wikiPageLength
|
1830
|
| http://dbpedia.org/ontology/wikiPageRevisionID
|
1116212485
|
| http://dbpedia.org/ontology/wikiPageWikiLink
|
http://dbpedia.org/resource/CP/M +
, http://dbpedia.org/resource/Category:User_interfaces +
, http://dbpedia.org/resource/Xerox_PARC +
, http://dbpedia.org/resource/Word-processing +
, http://dbpedia.org/resource/Mouse_%28computing%29 +
, http://dbpedia.org/resource/Backup +
, http://dbpedia.org/resource/Computer_program +
, http://dbpedia.org/resource/User_interface +
, http://dbpedia.org/resource/Menu_%28computing%29 +
, http://dbpedia.org/resource/WordStar +
, http://dbpedia.org/resource/Screenshot +
, http://dbpedia.org/resource/Massachusetts_Institute_of_Technology +
, http://dbpedia.org/resource/Keystroke +
, http://dbpedia.org/resource/Markup_language +
|
| http://dbpedia.org/property/wikiPageUsesTemplate
|
http://dbpedia.org/resource/Template:About +
, http://dbpedia.org/resource/Template:Citation_needed +
, http://dbpedia.org/resource/Template:Unreferenced +
, http://dbpedia.org/resource/Template:Soft-eng-stub +
|
| http://purl.org/dc/terms/subject
|
http://dbpedia.org/resource/Category:User_interfaces +
|
| http://www.w3.org/ns/prov#wasDerivedFrom
|
http://en.wikipedia.org/wiki/Reactive_user_interface?oldid=1116212485&ns=0 +
|
| http://xmlns.com/foaf/0.1/isPrimaryTopicOf
|
http://en.wikipedia.org/wiki/Reactive_user_interface +
|
| owl:sameAs |
http://dbpedia.org/resource/Reactive_user_interface +
, http://yago-knowledge.org/resource/Reactive_user_interface +
, https://global.dbpedia.org/id/4toz1 +
, http://www.wikidata.org/entity/Q7300320 +
, http://rdf.freebase.com/ns/m.0h66j3 +
|
| rdf:type |
http://dbpedia.org/class/yago/Communication100033020 +
, http://dbpedia.org/class/yago/Abstraction100002137 +
, http://dbpedia.org/class/yago/CodingSystem106353757 +
, http://dbpedia.org/class/yago/WrittenCommunication106349220 +
, http://dbpedia.org/class/yago/Program106568978 +
, http://dbpedia.org/class/yago/Software106566077 +
, http://dbpedia.org/class/yago/Interface106575227 +
, http://dbpedia.org/class/yago/Code106355894 +
, http://dbpedia.org/class/yago/WikicatUserInterfaces +
, http://dbpedia.org/class/yago/Writing106359877 +
|
| rdfs:comment |
A human-to-computer user interface is said … A human-to-computer user interface is said to be "reactive" if it has the following characteristics: 1.
* The user is immediately aware of the effect of each "gesture". Gestures can be keystrokes, mouse clicks, menu selections, or more esoteric inputs. 2.
* The user is always aware of the state of his/her data. Did I just save those changes? Did I just overwrite my backup by mistake? No data is hidden. In a figure-drawing program, the user can tell whether a line segment is composed of smaller segments. 3.
* The user always knows how to get help. Help may be context-sensitive or modal, but it is substantial. A program with a built-in help browser is not reactive if its content is just a collection of screen shots or menu item labels with no real explanation of what they do. with no real explanation of what they do.
|
| rdfs:label |
Reactive user interface
|
