Introduction to GUI Programming with Swing

Many programming courses include small example files whose job is not to solve a large problem but to show a few ideas in action. This article looks at one such file, named GUIDemo.java. Before reading any further, try to predict what it is about using only its name.

The word graphical is the key difference from a program that only prints text. A GUI presents its controls visually, so a person can see them and act on them with a mouse or keyboard. The source uses this idea as the background for the whole section: GUIDemo.java is meant to show a few of these visual building blocks in action rather than teach a full application.

A useful way to read any demonstration is to follow, one step at a time, what the reader is supposed to take from it. Applied to GUIDemo.java, the source supplies information in a clear order. The timeline below traces that reading path.

The source describes the relationship in two layers. The Swing library is the larger body of GUI tools. The basic GUI components are a subset of those tools, the ones the demonstration chooses to display. GUIDemo.java sits on top of both, using some of the library's components to show how they are used.

Keep the three pieces distinct. Swing is the library, which is the collection of tools. The basic components are the pieces that library provides. GUIDemo.java is a program that shows some of those pieces. The library is the source, the components are what it supplies, and the demonstration is one place where a reader sees them used.

The source makes a specific claim about timing: you will not be able to understand GUIDemo.java until you have learned about GUI programming. This is a prerequisite relationship. A prerequisite is knowledge that another topic depends on. Here, the basic components are the content of the demonstration, and GUI programming is the framework that makes sense of that content.