HyperCard: An Object-Oriented Disappointment
Although HyperCard is claimed to be easy to use it has many limitations and curious features. It is further claimed to be ‘object oriented.’ This object orientation is also limited and curious. The disappointment is that HyperCard’s arbitrariness and limitations are technically unnecessary, indeed result in error prone constructions, slower execution, increased learning effort. Yet HyperCard is successful: we will never know how much more successful it might have been had its designers employed any programming language design principles.
Unable to display preview. Download preview PDF.
- Apple Inc., Human Interface Guidelines: The Apple Desktop Interface, Addison-Wesley, 1987.Google Scholar
- Apple Inc., Hyper Card Stack Design Guidelines, Addison-Wesley, 1989.Google Scholar
- M. C. Atkins & A. W. Brown, “Principles of Object-Oriented Systems,” Software Engineer’s Reference Book, J. A. McDermid, ed., pp39/1–39/13, Butterworth-Heinemann Ltd., 1991.Google Scholar
- Claris Corp., Hyper Card Script Language Guide, 2nd. edition, 1990.Google Scholar
- G. F. Coulouris & H. W. Thimbleby, HyperProgramming, Addison-Wesley, in press.Google Scholar
- J. Gervich, “How I Learned to Stop Worrying and Love Hyper Card,” in B. K. Laurel, ed., The Art of Human-Computer Interface Design, pp131–133, Addison-Wesley, 1990.Google Scholar
- II. W. Thimbleby, User Interface Design, Addison-Wesley, 1990.Google Scholar