Map
Index
Random
Help
th

QuoteRef: conkJ9_1987

topics > all references > ThesaHelp: references c-d



ThesaHelp:
references c-d
Topic:
examples of hypertext systems
Topic:
software documentation
Topic:
hypertext links
Group:
user interface for hypertext
Topic:
icons for a user interface
Group:
hypertext
Topic:
hypertext nodes
Topic:
display of hypertext links
Topic:
using keywords to search hypertext
Topic:
information retrieval by following links
Topic:
hypertext browser
Topic:
searching hypertext
Topic:
problems with disorientation in hypertext
Topic:
examples of manual hypertext systems
Topic:
cross reference and hierarchical links in hypertext
Topic:
size of hypertext nodes
Topic:
dictionary for natural language
Topic:
man-machine symbiosis
Topic:
hypertext as a global database
Topic:
outlines
Topic:
information filters
Topic:
linearization of hypertext
Topic:
types of hypertext links
Topic:
text trails through hypertext
Topic:
problem solving
Topic:
semantic networks
Topic:
arrow-jump keys for a UserInterface
Topic:
current position in a user interface; cursor
Topic:
help in UserInterface
Topic:
list processing
Topic:
history list in hypertext
Topic:
execution of hypertext nodes
Topic:
problems with reading hypertext
Topic:
hypertext subsets, webs, and contexts
Topic:
attachment of hypertext links
Topic:
collection class
Topic:
using a computer as a communication/information medium
Topic:
hypertext rhetoric
Topic:
problems with cognitive overhead of hypertext
Topic:
interactive response time
Topic:
non-hierarchical classification and multiple classification
Topic:
knowledge as interrelated facts
Topic:
hypertext nodes as facts
Topic:
using icons to represent objects in a user interface
Topic:
semi-structured text
Topic:
hypertext nodes made of names
Topic:
hierarchical structures in hypertext
Topic:
using icons to represent windows
Topic:
implementation of user interfaces
Topic:
problems with writing hypertext

Reference

Conklin, J., "Hypertext: an introduction and survey", Computer, September 1987, pp. 17-41. Google

Quotations
17 ;;Quote: Smithsonian Institute has a demonstration laboratory for hypertext
17 ;;Quote: linear organization not useful for program documentation; either squeezed into margin or breaks up program flow
18 ;;Quote: the essential feature of hypertext is machine-supported links
18 ;;Quote: hypertext windows usually correspond with nodes; but this is not important
19 ;;Quote: a hypertext consists of a network of textual nodes, a window per node, link icons, browsing, and modifiability
19 ;;Quote: hypertext nodes displayed as windows with the node's name or title
19 ;;Quote: a Hypertext window contains link icons with text that suggests the contents of its destination
19 ;;Quote: Hypertext browsed by following links, searching for keyword, or graphical browser
19 ;;Quote: in a complex Hypertext, it is easy to become lost; a graphical browser helps
20 ;;Quote: 3x5 index cards forms a manual Hypertext with cross-references and hierarchical bundling
20 ;;Quote: NoteCards modularize notes into small chunks
20 ;;Quote: a dictionary or encyclopedia is a manual Hypertext; i.e., a graph of textual nodes joined by referential links
20 ;;Quote: Hypertext was originally for ultimate human-computer interaction
20 ;;Quote: earliest visions of Hypertext was the integration of all knowledge; maintained by both authors and readers
22 ;;Quote: NLS files were a hierarchy of statements with reference links within or between files
22 ;;Quote: NLS used view filters to select information for from a hypertext database
22+ ;;Quote: NLS view filters by hierarchical depth, items per level, or content
24 ;;Quote: TEXTNET has a taxonomy of link types such as irrelevant, inadequate and rambling
24 ;;Quote: TEXTNET path is a default pathway through a Hypertext; avoids n-way decisions
24 ;;Quote: IBIS for analysis of 'wicked problems' without a single answer
25 ;;Quote: WE sees reading and writing as transforming linear, hierarchy, and network representations
26 ;;Quote: Hyperties always selects a link; cursor jumps to next link
27 ;;Quote: DocumentExaminer includes entire Lisp manual
27 ;;Quote: DocumentExaminer allows string search for keywords
27 ;;Quote: DocumentExaminer adds links to a list of current topics; follow a link by going to the list
28 ;;Quote: with Lisp can write new node types for NoteCards or action nodes which execute when accessed
28 ;;Quote: 50-100 users of NoteCards; one database had 1600 cards and 3500 links
29 ;;Quote: Intermedia must help users manage complex Hypertext environments
29 ;;Quote: multiple Intermedia links displayed as one link icon which can be queried
29 ;;Quote: each Intermedia link belongs to a set of webs and is visible only when a containing web is active
29 ;;Quote: Intermedia has a local map for links and nearest neighbors of a document
29+ ;;Quote: Intermedia has a global map for navigation anywhere in a Hypertext
29+ ;;Quote: Neptune links to a particular version or the latest version
29 ;;Quote: Neptune links to a byte offset at source and destination
29 ;;Quote: HAM nodes and links have attribute/value pairs for querying
31 ;;Quote: a collection is a linear sequence of segments defined explicitly or by a predicate
32 ;;Quote: Guide has replacement links, note links (in a window), and reference links
32 ;;Quote: Hypertext is a computer-based medium for thinking and communication
33 ;;Quote: Hypertext eases restrictions on location of an idea within a paper
33 ;;Quote: Hypertext nodes can correspond to objects in the world
33 ;;Quote: Hypertext links is a database method different from queries
33 ;;Quote: Hypertext is a semantic network that mixes informal text with mechanized operations
33 ;;Quote: in a Hypertext system, it should be easy to follow a link
33 ;;Quote: Hypertext access time is important since readers need to look at nodes to determine relevancy
35 ;;Quote: most Hypertext users want keyword or string search
35 ;;Quote: can define multiple, overlapping hierarchies for information elements
35 ;;Quote: Hypertext can view multiple nodes as one big node but segmenting the node into chunks is difficult
35 ;;Quote: a Hypertext node does not blend seamlessly with its neighbors (unlike paragraphs)
36 ;;Quote: Hypertext readers and writers must decide what links to pursue; best for branching applications
36 ;;Quote: a Hypertext node can be an object that represents an idea; it is linked, moved, or modified independently
36 ;;Quote: type nodes by color, size, or iconic form; provides visual categorization
36 ;;Quote: semistructured nodes are a template that assists user and computer
37 ;;Quote: composite node aggregates related nodes and links; can be collapsed into an icon
37 ;;Quote: display a composite node via a constraint language that describes interpane relationships, sizes and configurations
38 ;;Quote: disorientation problem: with Hypertext must know location and how to find information in the network
39 ;;Quote: Hypertext disorientation worse with many nodes and links, frequent changes, nonvisual users, etc.
39+ ;;Quote: Hypertext browser does not solve the disorientation problem
39 ;;Quote: avoid Hypertext disorientation by database search and query
39 ;;Quote: Hypertext can filter information to reduce the level of complexity and detail
40 ;;Quote: Hypertext links require 'cognitive overhead' to create, name and keep track
40 ;;Quote: cognitive overhead since an association requires finding a word or phrase to summarize or suggest it or its relationship
40 ;;Quote: cognitive overhead since an association may require multiple links into the document
40 ;;Quote: reading a Hypertext requires choosing which links to follow; these metalevel decisions are not needed in linear texts
40 ;;Quote: cognitive overhead in Hypertext is reduced by rapid access (KMS), short descriptions (Intermedia), and graphical browsers
40 ;;Quote: problems of Hypertext are disorientation and cognitive overhead
40+ ;;Quote: cognitive overhead in Hypertext is the effort needed to juggle several tasks and trails
40+ ;;Quote: disorientation in a Hypertext is losing one's sense of location and direction


Related Topics up

ThesaHelp: references c-d (337 items)
Topic: examples of hypertext systems (25 items)
Topic: software documentation (64 items)
Topic: hypertext links (45 items)
Group: user interface for hypertext   (5 topics, 110 quotes)
Topic: icons for a user interface (23 items)
Group: hypertext   (44 topics, 786 quotes)
Topic: hypertext nodes (19 items)
Topic: display of hypertext links (15 items)
Topic: using keywords to search hypertext (26 items)
Topic: information retrieval by following links (23 items)
Topic: hypertext browser (23 items)
Topic: searching hypertext (17 items)
Topic: problems with disorientation in hypertext (18 items)
Topic: examples of manual hypertext systems (6 items)
Topic: cross reference and hierarchical links in hypertext (9 items)
Topic: size of hypertext nodes (8 items)
Topic: dictionary for natural language (41 items)
Topic: man-machine symbiosis (46 items)
Topic: hypertext as a global database (30 items)
Topic: outlines (16 items)
Topic: information filters (22 items)
Topic: linearization of hypertext (23 items)
Topic: types of hypertext links (19 items)
Topic: text trails through hypertext (17 items)
Topic: problem solving (32 items)
Topic: semantic networks (42 items)
Topic: arrow-jump keys for a UserInterface (5 items)
Topic: current position in a user interface; cursor (23 items)
Topic: help in UserInterface (33 items)
Topic: list processing (15 items)
Topic: history list in hypertext (26 items)
Topic: execution of hypertext nodes (21 items)
Topic: problems with reading hypertext (9 items)
Topic: hypertext subsets, webs, and contexts (12 items)
Topic: attachment of hypertext links (16 items)
Topic: collection class (11 items)
Topic: using a computer as a communication/information medium (32 items)
Topic: hypertext rhetoric (17 items)
Topic: problems with cognitive overhead of hypertext (20 items)
Topic: interactive response time (32 items)
Topic: non-hierarchical classification and multiple classification (16 items)
Topic: knowledge as interrelated facts (23 items)
Topic: hypertext nodes as facts (6 items)
Topic: using icons to represent objects in a user interface (10 items)
Topic: semi-structured text (17 items)
Topic: hypertext nodes made of names (13 items)
Topic: hierarchical structures in hypertext (19 items)
Topic: using icons to represent windows (15 items)
Topic: implementation of user interfaces (18 items)
Topic: problems with writing hypertext (12 items)

Collected barberCB 10/87 3/89
Copyright © 2002-2008 by C. Bradford Barber. All rights reserved.
Thesa is a trademark of C. Bradford Barber.