fonts, the section focuses on images. It closes by discussing AWT's support for data
Before JDK 1.0's release (on January 23, 1996), developers at Sun Microsystems
were tasked with abstracting the various windowing systems of the day and their
attendant widgets (GUI controls, such as buttons—Java refers to GUI controls as
components ) into a portable windowing system that Java applications could target.
AWT was born and was included in JDK 1.0. (Legend has it [see ht-
plemented in one month.)
to GUI events (such as button clicks and key presses). Subsequent JDK releases
6 introduced the Desktop, Splash Screen, and System Tray APIs, and JDK 7 stand-
date 10 (build 12).
Appendix C covers Desktop, Splash Screen, System Tray, and translucent/shaped
AWT uses toolkits to abstract over windowing systems. A toolkit is a concrete imple-
mentation of AWT's abstract java.awt.Toolkit class. AWT provides a separate
For example, void beep() emits an audio beep.
Mostapplicationsshouldnotcallanyof Toolkit 'smethodsdirectly;theyareinten-
ded for use by AWT. However, you might occasionally find it helpful to call some of