Lab 16: GUI Part II

0. Finishing up

Before starting on today's lab, finish up Lab 15 from last Friday.

1. Introduction and setup

The goal of this lab is to design windows requesting input from the user.

Today we go back to a simulation of the same sort as the predator-prey example and the ball-catching project. We will have a grid inhabited by agents, each acting in its own way.

The grid we'll be working with today will be inhabited by Sprites. A Sprite is an object that moves about the grid in a way determined by the following parameters:

• A direction. The direction in which a sprite is going will be represented in radians, the same way polar coordinates are specified: 0 (or 2π) means straight east, .25π means north east, .5π means straight north, π means straight west, etc.
• A velocity. A Sprite has a speed in terms of the number of grid positions per unit time. We will keep this as a double, and it will refer to the distance the Sprite will try to move in its direction. Of course, the Sprite actually moves a certain amount in the x dimension and a certain amount in the y dimension. The change in x and y are calculated from the velocity and direction (don't worry, that part is already programmed for you--but you may look at it if you're interested.).
• A rotational velocity. A Sprite is also constantly turning. During every move, it changes its direction by a constant amount, which is its rotational velocity. The rotational velocity is also expressed in radians. (A Sprite whose rotational velocity is 0 is moving in a straight line.)

Make a directory for this lab and copy the appropriate files from the course directory.

hg clone /cslab/class/csci235/lab16
cd lab16

Then compile and run the program Sprites. Notice that there is a jar file; you'll need to refer to it on the command line when you compile and run.

javac -cp simulation.jar:. Sprites.java
java -cp simulation.jar:. Sprites

By default there is a single Sprite. If you inspect the code in Sprites.java, you'll see that the Sprite is added to the grid in the line

model.setAgentAt(100, 100, new Sprite(100, 100, .25 * Math.PI, .125 * Math.PI,
                                     3, Color.RED, model));

Compare this with the file Sprite.java, particularly the instance variables and constructor, to understand all that this means.

The intent of this program is to allow the user to add new Sprites to the system as the simulation runs. Pressing the button Add Sprite should launch a dialog box asking the user for all the specification of the Sprite and add that Sprite to the grid. However, when you press the button, nothing happens. That's for you to write.

("Dialog box" is not meant to be a technical term; it just means a smallish window on the screen temporarily to get input from the user.)

Read the entire lab description before you start writing any code. It will help you to see the program as a whole, and there are also some hints lurking toward the end.

2. The AddListener class

The Add Sprite button has an action listener attached to it. However, the actionPerformed() method is empty. Your main task is to fill in this method, which will prompt the user with a dialog box.

As you add things to the window in your program, It is a good idea to periodically compile and run the program to see how the window looks so far, and then make some adjustments. Make the window look reasonably nice; play with the dimensions and the layout until it looks right.

Here are things that ought to be in the dialog box:

• Ultimately, we want the user to be able to choose a color for this Sprite. The easiest way to do this is to use a new Java GUI class called JColorChooser. This displays a color palette which the user may click on to select a color. Then the program can read that color from the JColorChooser object. Go to the Java API to find out more about this class. Mainly you will want to use the no-parameter constructor and the method getColor().
• There must be textfields for the direction, rotational velocity, and the velocity, as well for the initial x and y position.

  We have not used the class JTextField before; you can think of it as being like a JLabel, except that it displays with a box, and the user is permitted to type in it. The essential methods—including constructors—were described on the GUI handout from class.

  Since it will be hard to indicate a value including π when entering a direction or rotational velocity, you should interpret the user's input in these fields as a coefficient of π. In other words, if the user enters ".5" into the direction field, you should interpret that to mean ".5π". Also, all these text fields should have an accompanying appropriate label.

• There should be a button for the user to press when the dialog is finished, labeled something like Ok.

The actionPerformed() method should also make the dialog box appear and it should attach another action listener to the Ok button, but that action listener will be the subject of the next part.

3. The other action listener class

Write another class, also implementing ActionListener which will react to the Ok button being pressed. Specifically, the actionPerformed() method should

• close the dialog box (to do this, call setVisible(false)).
• read information from the textfields of the dialog box.
• add a new Sprite to the grid.

First, you should think about what pieces of information this action listener needs to know (hint: a lot). These will become instance variables and parameters to the constructor. Then writing the actionPerformed() method will be easier.

4. Some tips

The JColorChooser is bigger than you might guess. You probably want to your other components into a single panel with its own layout, and put that and the color chooser into your window with a flow layout.

An awkward thing about building a dialog this way is that it is hard to know in advance how big the components in your window should be. But if you choose your layout classes appropriately, you can do a first version without worrying about getting the window size exactly right. You can run that program and resize the window to make it look good. Once you have that, you can use the command xwininfo to find out the size. Run the command in a terminal window, then click on the window you want to find out about.

5. Turn-in

Turn in the source files you created or modified with a command such as

/cslab/class/csci235/bin/handin lab16 *.java

Be sure to include all of your files on a single command.