There are two basic sets of components that a user uses to build Java programs. These two groups of components are called Abstract Window Toolkit (AWT) and Swing. Both of these groups of components are part of the Java Foundation Classes (JFC).
| AWT (Abstract Window Toolkit) | Swing |
|---|---|
| Use of native peers speeds component performance of AWT. | Swing components are generally slower and buggier than AWT. |
| AWT components more closely reflect the look and feel of the OS they run on. | The pluggable look and feel lets a user design a single set of GUI components that can automatically have the look and feel of any OS platform. |
| AWT applets can run without the Java plug-in. | Most Web browsers do not include the Swing classes, so the Java plug-in must be used. |
| Use of native peers creates platform specific limitations. Some components may not function at all on some platforms. | Pure Java design provides for fewer platform specific limitations. |
| AWT components do not support features such as icons and tool-tips. | Swing supports a wider range of features such as icons and pop-up tool-tips for components. |
| There is a much smaller set of AWT components available; thus, it places the burden on the programmer to create his or her own AWT-based components. | There is a huge set of Swing components available; thus, it removes the burden on the programmer to create his or her own AWT-based components. |
| The majority of component makers base their new component development on Swing components. | Swing development is more active. Sun puts much more energy into making Swing robust. |
Like this article? Share it with others
If you like this article, please leave a comment or subscribe this blog via RSS or via e-mail, Bookmark and share through your network. Click the AddThis button below. Thanks.
If you like this article, please leave a comment or subscribe this blog via RSS or via e-mail, Bookmark and share through your network. Click the AddThis button below. Thanks.
