Java, Java, Java

 

 

 

 

 

 

As we saw in Chapter 4, whatever happens while the computer is running is classified as an event. Every keystroke and mouse click, every time a disk is inserted into a disk drive, an event is generated. The handling of events are an important element of GUI programming. Therefore, before we begin discussing how to design GUIs, it will be useful to review the main concepts of Java’s event model.

When a Java program is running, events generated by the hardware are passed up through the operating system (and through the browser, for applets) to the program. Those events that belong to the program must be handled by the program (refer to Fig. 4.18 in Chapter 4). For example, if you click your browser’s menu bar, that event will be handled by the browser itself. If you click a button contained in the Java program, that event should be handled by the program.

In Java, whenever something happens within a GUI component, an event object is generated and passed to the event listener that has been registered to handle that component’s events. You’ve seen numerous ex- amples of this process in earlier chapters, but we’ve included a simple example to serve as a reminder.

Suppose you create a JButton in a GUI as follows:

,,

 

J

Whenever the user clicks the JButton, an ActionEvent is generated. In order to handle these events, the GUI must register the JButton with a listener object that listens for action events. This can be done in an ap- plet’s init() method or in an application’s constructor method, as in this example:

,,

 

 

>Listener

 

J

In this case, we have designated the GUI itself (this) as an ActionListener for clickme (Fig. 13.5). A listener is any object that implements a listener

 

interface, which is one of the interfaces derived from java.util.Event-

Listener. An ActionListener is an object that listens for and receives

 

Figure 13.5: The GUI listens for action events on the JButton.

ActionEvents.

 

In order to complete the event-handling code, the GUI must imple- ment the ActionListener interface. As Figure 13.6 shows, implement- ing an interface is a matter of declaring the interface in the class heading and implementing the methods contained in the interface, in this case the actionPerformed() method.

 

 

 

 

 

 

,,

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

J

Figure 13.6: A simple GUI application that handles action events on a

JButton.

 

 

 

 

 

 

Now that we have implemented the code in Figure 13.6, whenever the user clicks clickme, that action is encapsulated within an ActionEvent object and passed to the actionPerformed() method. This method contains Java code that will handle the user’s action in an appropriate way. For this example, it modifies the button’s label by appending an asterisk to it each time it is clicked. Figure 13.7 depicts the sequence of actions and events that occur when the the user clicks a button.

 

Figure 13.7: A UML depiction of the sequence of actions and events that take place when a button is clicked. The vertical lines repre- sent time lines, with time running from top to bottom. The arrows between lines represent messages passing between objects.

 

 

 

 

 

showStatus(s:String)

 

 

 

The methods used to handle the ActionEvent are derived from the java.util.EventObject class, the root class for all events (Fig. 13.8). Our example (Fig. 13.6) uses the getSource() method to get a reference to the object that generated the event. To see what information is con- tained in an event object, we can use the toString() method to print

a string representation of the event that was generated. Here’s what it

displays:

 

Figure 13.8: An EventObject. The getSource() method is used to get the object that caused the event.

,,

 

 

J

 

As you can see, the event generated was an ACTION PERFORMED event, in response to the ClickMe command. The source of the event was the JButton.

Event Classes

Although the event model is the same for both AWT and Swing classes, the Swing package introduces many additional events. Table 13.1 lists the events that are generated by both AWT and Swing components. You already have worked with some of these. We have written GUIs that handled ActionEvents for JButtons and JTextFields in preceding chapters.

In viewing Table 13.1, it’s important to remember that the classes listed there are arranged in a hierarchy. This will affect the events that a par- ticular object can generate. For example, a JButton is a JComponent (Fig. 13.2), so in addition to generating ActionEvents when the user clicks on it, it can also generate MouseEvents when the user moves the mouse over it. Similarly, because a JTextField is also a JComponent, it can generate KeyEvents as well as ActionEvents.

Note that the more generic events, such as those that involve moving,

focusing, or resizing a component, are associated with the more generic components. For example, the JComponent class contains methods that are used to manage ComponentEvents. Because they are subclasses of JComponent, JButtons and JTextFields can also use these meth-

 

TABLE 13.1 Java’s AWTEvents for each Component type (Original source: David Flanagan,

Java in a Nutshell, 2d ed., O’Reilly Associates, 1997. Modified for Swing components.)

 

 

ods. Defining the more generic methods in the JComponent superclass is another example of the effective use of inheritance.

 

Table 13.2 lists events that are new with the Swing classes. Some of the events apply to new components. For example, JTable and JTree do not have AWT counterparts. Other events provide Swing components with capabilities that are not available in their AWT counterparts. For ex- ample, a CaretEvent allows the programmer to have control over mouse clicks that occur within a text component.

 

TABLE 13.2 Some of the events that are defined in the Swing library.

 

 

Tables 13.1 and 13.2 provide only a brief summary of these classes and Swing components. For further details you should consult the JDK online documentation at

,,

 

J

 

SELF-STUDY EXERCISES

EXERCISE 13.2 Is it possible to register a component with more than one listener?

EXERCISE 13.3 Is it possible for a component to have two different kinds of listeners?