Java GUI Components

A graphical user interface, or GUI, is the part of a program that a person sees and interacts with on screen. Windows, push buttons, and text fields are typical examples. A GUI is not a picture that sits still and quietly does its job. It has to be used. The source material makes this point directly: a graphical user interface does not respond because a user merely looks at it. Something must happen through interaction, such as a push button being clicked or a keyboard key being pressed.

Before defining the terms, trace what happens from start to finish when a user clicks a push button. Each step below is stated in the source material. Read the diagram from left to right, then check it against the numbered steps that follow.

The diagram is a trace of one event, not a fixed rule about every GUI. Its purpose is to show that the user, the component, the event, the message, and the handler each play a distinct role. Keep the trace in mind, because the next sections name each part and then trace a second, different interaction through the same pipeline.

These three ideas fit together in a fixed order. The cause is an interaction. The notification is a message. The response is the handler. Because the source adds that a GUI program typically consists largely of event handlers, you can read most of a typical GUI program as a collection of responses to events rather than as one long sequence of instructions that runs from top to bottom.

A Java GUI component, such as a push button, is an object rather than an unrelated piece of screen decoration. This is the reason a component can be clicked, can notify the program about an event, and can be used again wherever it is needed. The source states that Java GUI components are objects, and it adds that Java provides many predefined classes representing different kinds of GUI components.

Some of the predefined component classes are subclasses of other classes. This means the component classes are not a flat list. They form a class structure in which one class can build on another. The source says the component classes have relationships to one another within that structure. It does not list which classes those are, so this article does not name them.

The source describes three things that are easy to confuse. The Swing library is the larger body of GUI tools. The basic GUI components are the pieces that Swing provides, and they are a subset of those tools. GUIDemo.java is a program that shows some of those basic components in action. Read the diagram from the top down, with the library at the top and the demonstration below it.

The relationship has two layers. The library and its components form the foundation. GUIDemo.java sits on top of both and uses some of those components to show how they are used. The arrow from GUI programming in the diagram is not a step in the program. It is a warning about what you need before the demonstration makes full sense.

A useful way to read a demonstration is to trace what it is meant to show, one step at a time. Start with the name. GUIDemo.java tells you it concerns GUIs and that it is a demo. The source then describes it as a simple demonstration of some basic GUI components from the Swing library. Finally, the source places it in Section 1.6 and says it cannot be understood until you have learned GUI programming.

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

The practical consequence is that reading the demonstration early will show you what the components look like, but it will not explain why the program is organized the way it is. The events, messages, and handlers from the first sections are the framework that would give the code its meaning. Without that framework, a reader can see the pieces but cannot yet follow how they respond to interaction.