Lesson plan

Appearance Manager

The Appearance Manager is a component of Mac OS 8 and Mac OS 9 that controls the overall look of the Macintosh graphical user interface widgets and supports several themes. It was originally developed for Apple's ill-fated Copland project, but with the cancellation of this project the system was moved into newer versions of the Mac OS. The Appearance Manager is also available free as part of a downloadable SDK for System 7. The Appearance Manager is implemented as an abstraction layer between the Control Manager and QuickDraw. Previously, controls made direct QuickDraw calls to draw user interface elements such as buttons, scrollbars, window title bars, etc. With the Appearance Manager, these elements are abstracted into a series of APIs that draw the item as a distinct entity on behalf of the client code, thus relieving the Control Manager of the task. This extra level of indirection allows the system to support the concept of switchable "themes", since client code simply requests the image of an interface element (a button or scroll bar, for example) and draws its appearance. Kaleidoscope, a 3rd party application, was the first to utilize this functionality with via "scheme" files, followed by an updated Appearance Control Panel in Mac OS 8.5, which acted similarly via "theme" files. Schemes and themes are similar in concept, but they are not internally compatible.…

Back to article

Article summary

The Appearance Manager is a component of Mac OS 8 and Mac OS 9 that controls the overall look of the Macintosh graphical user interface widgets and supports several themes. It was originally developed for Apple's ill-fated Copland project, but with the cancellation of this project the system was moved into newer versions of the Mac OS. The Appearance Manager is also available free as part of a downloadable SDK for System 7. The Appearance Manager is implemented as an abstraction layer between the Control Manager and QuickDraw. Previously, controls made direct QuickDraw calls to draw user interface elements such as buttons, scrollbars, window title bars, etc. With the Appearance Manager, these elements are abstracted into a series of APIs that draw the item as a distinct entity on behalf of the client code, thus relieving the Control Manager of the task. This extra level of indirection allows the system to support the concept of switchable "themes", since client code simply requests the image of an interface element (a button or scroll bar, for example) and draws its appearance. Kaleidoscope, a 3rd party application, was the first to utilize this functionality with via "scheme" files, followed by an updated Appearance Control Panel in Mac OS 8.5, which acted similarly via "theme" files. Schemes and themes are similar in concept, but they are not internally compatible.…

Key claims

No claims recorded.

Discussion questions

  1. Summarise the article in your own words. Which single claim would you verify first, and why?
  2. Which claim in this article is most likely to be revised as the sources update? How would you check its current status?
  3. If two sources disagreed about one of these facts, what would you need in order to trust one over the other?

Bibliography

No sources recorded.

Key claims and bibliography are generated from the same tracked claims and sources as the article page.