16.2.5. Event Handling in AWT

• Based on Delegation Event Model.

AWT uses the Delegation Event Model for handling events. In this model, events are generated by components (like buttons), and instead of handling these events directly, we delegate the responsibility of handling to separate listener objects. This means that when an event occurs (like a button click), the component that generated the event will notify its associated listener, which contains the logic to respond to that event.

Think of a waiter in a restaurant. When a customer orders food (the event), the waiter (the listener) takes the order and communicates it to the kitchen (the event's response). The waiter doesn’t cook the food; they pass the order to someone else who does. Similarly, in AWT, components pass events to their listeners.

• Components generate events.

In AWT, various components like buttons, text fields, and checkboxes can generate events. For example, when a button is clicked, it generates an ActionEvent. Different types of components generate different types of events; for instance, a mouse click generates a MouseEvent, while typing in a text field generates a KeyEvent. Each of these events carries information about what happened, such as the type of event and the component that triggered it.

Imagine a doorbell at your home. When someone presses it (the event), it rings (the response). Different buttons can be thought of as different types of doorbells, each creating a distinct sound or action when pressed.

• Listeners handle them.

Listeners are special objects in AWT that wait for events to occur and define what should happen when an event occurs. You add a listener to a component by calling a method like addActionListener, passing in the listener as an argument. The listener then implements an interface (such as ActionListener) with methods like actionPerformed, where you specify the actions to be taken when an event occurs. This separation of the event generation and handling logic promotes cleaner and more maintainable code.

Continuing with the restaurant analogy, when an order is taken (event generation), the chef (listener) has a specific recipe (code) to prepare the food when the order comes in. The chef doesn’t decide how to take the order; they just focus on cooking the dish.

Button b = new Button("Click"); b.addActionListener(new ActionListener() { public void actionPerformed(ActionEvent e) { System.out.println("Button clicked!"); } });

In this code snippet, we create a Button object named 'b' with the label 'Click'. We then add an ActionListener to the button which listens for click events. When the button is clicked, the actionPerformed method is triggered, executing the code inside it, which prints 'Button clicked!' to the console. This is a simple example of event handling in AWT where an action performed by the user (button click) results in a specific behavior (printing a message).

Think of a light switch. When you press the switch (event), it turns the light on (defined action). The button click in your code is like someone turning on the light, where the 'actionPerformed' method is defined to perform that action.

--