Graphical Programs

1. Introduction Graphical programs require a very different programming model to the non-graphical programs we have encountered in the past. A non-graphical program typically runs straight through from beginning to end. By contrast, a graphical program should be capable of running indefinitely, accepting input through the graphical user interface (GUI) and responding accordingly. This kind of programming is known as event-driven programming, because the program's sequence of operation is determined by events generated by the GUI components. The program responds to events by invoking functions known as event handlers . For example, pushing the Print button may generate a "button-pushed" event, which results in a call to an event handler named print(). In general, a graphical program consists of the following key elements: Code to create GUI components, such as buttons, text areas, scrollable views, etc. Code that lays out the components within a container. Examples of containers are frames, which are stand-alone windows, and applets, which are windows that are embedded within a web page. Event handling code that specifies what should happen when the user interacts with the GUI components. An event loop, whose job is to wait for events to occur and to call appropriate event handlers. The following pseudo-code illustrates how the event loop might work     while (true) {                                        // The event loop.         // Get the next event from the event queue.         Event e = get_next_event();         // Process the events by calling appropriate event handlers.         if (e.eventType == QUIT) {             exit();                                           // Terminate the program.         }         else if (e.eventType == BUTTON_PUSHED) {             if (e.eventSource == PRINT_BUTTON)                 print(e);                                   // Print out the current page.             else {                 ...             }         }         else {             ...         }     } In C++, the programmer must often explicitly write an event loop similar to the one shown above. This can involve a lot of work, so Java® attempts to shield the programmer from the actual event loop, while still providing a flexible way to specify how events are processed. 2. The Java® Event Model (JDK 1.1 and above) (Ref.  Java® Tutorial ) The Java® event model is based on the notion of event sources and event listeners. An event source is most frequently a user interface component (such as a button, menu item or scrollable view), which can notify registered listeners when events of interest occur. Note that an event source may generate both high level events e.g. button click, as well as low level events, e.g. mouse press. An event listener is an object that can register an interest in receiving certain types of events from an event source. The event source sends out event notifications by calling an appropriate event handling method in the event listener object. The event listener registration and notification process takes place according to event type . An object wishing to listen to events of a particular type must implement the corresponding event listener interface . The interface simply specifies a standard set of event handling functions that the listener object must provide. Here is a list of events, and their corresponding event types and event listener interfaces. EVENT EVENT TYPE EVENT LISTENER INTERFACE Button click, menu selection, text field entry ActionEvent ActionListener Resizing, moving, showing or hiding a component ComponentEvent ComponentListener Mouse press, mouse release, mouse click, mouse enter, mouse exit MouseEvent MouseListener Mouse move, mouse drag MouseEvent MouseMotionListener Key press, key release KeyEvent KeyListener Gain keyboard focus, lose keyboard focus FocusEvent FocusListener Window closing, window iconified, window deiconified WindowEvent WindowListener Scrolling AdjustmentEvent AdjustmentListener Item selection e.g. checkbox, list item ItemEvent ItemListener Return key pressed TextEvent TextListener Adding/removing a component to/from a container ContainerEvent ContainerListener

The general approach to implementing an event listener is the same in every case.

• Write a class that implements the appropriate XXXListener interface.
• Create an object of type XXXListener.
• Register the event listener object with an event source by calling the event source's addXXXListener method.

The following example shows how to create a frame. When the frame is closed, we want to make sure that the program terminates, since this does not happen automatically. We can use a WindowListener to do this.

import javax.swing.*;
import java.awt.event.*;

 public class Main {
    public static void main(String[] args) {
        // Create a window.  Then set its size and make it visible.
        JFrame frame = new JFrame("Main window");
        frame.setSize(400,400);
        frame.setVisible(true);

        // Make the program terminate when the frame is closed.  We do this by registering a window listener
        // to receive WindowEvents from the frame.  The window listener will provide an event handler called
        // windowClosing, which will be called when the frame is closed.
        WindowListener listener = new MyWindowListener();                 // A class that we write.
        frame.addWindowListener(listener);
    }
}

// Here is our window listener.  We are only interested in windowClosing, however, we must provide
// implementations for all of the methods in the WindowListener interface.
class MyWindowListener implements WindowListener {
    public void windowClosing(WindowEvent e) {
        System.out.println("Terminating the program now.");
        System.exit(0);
    }
    public void windowClosed(WindowEvent e) {}
    public void windowOpened(WindowEvent e) {}
    public void windowActivated(WindowEvent e) {}
    public void windowDeactivated(WindowEvent e) {}
    public void windowIconified(WindowEvent e) {}
    public void windowDeiconified(WindowEvent e) {}
}
 

Unfortunately, this example involves quite a lot of code. There are a couple of ways to simplify the program


Anonymous Classes

An anonymous class is a class that has no name. It is declared an instantiated within a single expression. Here is how we could use an anonymous class to simplify the closable frame example:

import javax.swing.*;
import java.awt.event.*;

 public class Main {
    public static void main(String[] args) {
        // Create a window.  Then set its size and make it visible.
        JFrame frame = new JFrame("Main window");
        frame.setSize(400,400);
        frame.setVisible(true);

        // Make the frame closable.  Here we have used an anonymous class that implements the
        // WindowListener interface.
        frame.addWindowListener(new WindowListener() {
            public void windowClosing(WindowEvent e) {
                System.out.println("Terminating the program now.");
                System.exit(0);
            }
            public void windowClosed(WindowEvent e) {}
            public void windowOpened(WindowEvent e) {}
            public void windowActivated(WindowEvent e) {}
            public void windowDeactivated(WindowEvent e) {}
            public void windowIconified(WindowEvent e) {}
            public void windowDeiconified(WindowEvent e) {}
        });
    }
}


Event Adapters

An event adapter is just a class that implements an event listener interface, with empty definitions for all of the functions. The idea is that if we subclass the event adapter, we will only have to override the functions that we are interested in. The closable frame example can thus be shortened to:

import javax.swing.*;
import java.awt.event.*;

 public class Main {
    public static void main(String[] args) {
        // Create a window.  Then set its size and make it visible.
        JFrame frame = new JFrame("Main window");
        frame.setSize(400,400);
        frame.setVisible(true);

        // Make the frame closable.  Here we have used an anonymous class that extends WindowAdapter.
        frame.addWindowListener(new WindowAdapter() {
            public void windowClosing(WindowEvent e) {    // This overrides the empty base class method.
                System.out.println("Terminating the program now.");
                System.exit(0);
            }
        });
    }
}


3. Laying Out User Interface Components

Containers

(Ref.  Java® Tutorial )

A Container is a GUI component that can hold other GUI components. Three commonly used container classes are

JFrame - This is a stand-alone window with a title bar, menubar and a border. It is typically used as the top-level container for a graphical Java® application.

JApplet - This is a container that can be embedded within an HTML page. It is typically used as the top-level container for a Java® applet.

JPanel - This is a container that must reside within another container. It provides a way to group several components (e.g. buttons) as a single unit, when they are laid out on the screen.  JPanel can also be used as an area for drawing operations. (When used in this way, it can provide automatic double buffering, which is a technique for producing flicker-free animation.)

A component object, myComponent, can be added to a container object, myContainer, using a statement of the form

    myContainer.getContentPane().add(myComponent);

The following example illustrates how to add a JButton instance to an instance of JFrame.

import javax.swing.*;
import java.awt.event.*;

 public class Main {
    public static void main(String[] args) {
        // Create a window.
        JFrame frame = new JFrame("Main window");
        frame.setSize(400,400);

        // Create a button and add it to the frame.
        JButton button = new JButton("Click me");
        frame.getContentPane().add(button);

        // Add an event handler for button clicks.
        button.addActionListener(new ActionListener() {
            public void actionPerformed(ActionEvent e) {      // Only one method to implement.
                System.out.println(e.getActionCommand());     // Prints out "Click me".
            }
        });

        // Make the frame closable.
        frame.addWindowListener(new WindowAdapter() {
            public void windowClosing(WindowEvent e) {
                System.exit(0);
            }
        });

        // Make the frame visible after adding the button.
        frame.setVisible(true);
    }
}


Layout Managers

(Ref.  Java® Tutorial )

Our previous example has only one interesting GUI component: a JButton . What if we wanted to add a second JButton and perhaps a JTextArea, so that we can display the message through the GUI? We can control the layout of these components within the container by using a layout manager. Java® comes with six layout managers (five in java.awt and one in javax.swing)

FlowLayout - Lays out components in a line from left to right, moving to the next line when out of room. This layout style resembles the flow of text in a document.

BorderLayout - Lays out components in one of five positions - at the North, South, East or West borders, or else in the Center.

GridLayout - Lays out components in rows and columns of equal sized cells, like a spreadsheet.

GridBagLayout - Lays out components on a grid without requiring them to be of equal size. This is the most flexible and also the most complex of all the layout managers.

CardLayout - Lays out components like index cards, one behind another. (No longer useful, now that Swing provides a JTabbedPane component.)

BoxLayout - Lays out components with either vertical alignment or horizontal alignment. (A new layout manager in Swing.)

It is also possible to set a null layout manager and instead position components by specifying their absolute coordinates using the method

    public void setLocation(int x, int y)