Get 20M+ Full-Text Papers For Less Than $1.50/day. Start a 14-Day Trial for You or Your Team.

Learn More →

A layout abstraction for user-system interface

A layout abstraction for user-system interface The strict separation of the functionality of a system from the user-system interface is considered as a reasonable design principle. One promising way to enforce the separation is to supply the system designer with a "user interface toolkit", a set of integrated software tools for implementing the user-system interface. The difficulty resides in determining the "right" abstractions to be implemented by the toolkit. So far, there is no satisfactory answer to this problem, only propositions. Little has been proposed for object-oriented I/O as a toolkit facility. Yet, applications are currently bound to express I/O in terms of low level abstractions. As a result, they are in charge of tasks that are irrelevant to their functionality. In this paper, we propose the Box as a mechanism to permit applications to handle I/O in terms of their own abstractions and to be relieved from irrelevant tasks. The box mechanism has been implemented and integrated in a user interface toolkit. http://www.deepdyve.com/assets/images/DeepDyve-Logo-lg.png ACM SIGCHI Bulletin Association for Computing Machinery

A layout abstraction for user-system interface

Coutaz, Joëlle
ACM SIGCHI Bulletin , Volume 16 (3) – Jan 1, 1985
Download PDF
7 pages

Loading next page...
 
/lp/association-for-computing-machinery/a-layout-abstraction-for-user-system-interface-kJkWb3Vysj

References (11)

Publisher
Association for Computing Machinery
Copyright
Copyright © 1985 by ACM Inc.
ISSN
0736-6906
DOI
10.1145/1044201.1044202
Publisher site
See Article on Publisher Site

Abstract

The strict separation of the functionality of a system from the user-system interface is considered as a reasonable design principle. One promising way to enforce the separation is to supply the system designer with a "user interface toolkit", a set of integrated software tools for implementing the user-system interface. The difficulty resides in determining the "right" abstractions to be implemented by the toolkit. So far, there is no satisfactory answer to this problem, only propositions. Little has been proposed for object-oriented I/O as a toolkit facility. Yet, applications are currently bound to express I/O in terms of low level abstractions. As a result, they are in charge of tasks that are irrelevant to their functionality. In this paper, we propose the Box as a mechanism to permit applications to handle I/O in terms of their own abstractions and to be relieved from irrelevant tasks. The box mechanism has been implemented and integrated in a user interface toolkit.

Journal

ACM SIGCHI Bulletin – Association for Computing Machinery

Published: Jan 1, 1985

There are no references for this article.