Personal Systems Image Application Architecture: Lessons Learned from the ImagEdit Program
暂无分享,去创建一个
Image applications require complex processing on large amounts of data. The application designer is presented with difficult challenges that are exacerbated on personal systems which have limited processor speed and constrained memory. This paper discusses the problems relevant to personal systems image application architecture and how these problems were solved in the ImagEdit® program. A virtual array manager (VAM) consisting of a virtual memory manager (VMM) and an access scheduler was used to solve the data management problem. The VAM divided each image into segments and transferred them to the VMM for storage. These segments were swapped between memory and disk in response to a sequence of access requests, controlled by the access scheduler using performance-maximizing heuristics. Object-oriented design was used to address the functional complexity problem. The processing functions were divided into two classes. The data-stream class included scanning, printing, and filing, with each data-stream function decomposed into a series of demand-driven pipe objects. The editing class included cut and paste, textual and graphical annotation, and freehand drawing.
[1] Richard M. Helms. Introduction to Image Technology , 1990, IBM Syst. J..
[2] Adele Goldberg,et al. SmallTalk 80: The Language , 1989 .
[3] Brad J. Cox,et al. Object-oriented programming ; an evolutionary approach , 1986 .
[4] Bjarne Stroustrup,et al. C++ Programming Language , 1986, IEEE Softw..
[5] Yuji Hakeda. The Image Object Content Architecture , 1990, IBM Syst. J..