Due: 2:00 P.M., Friday, 12/03/10

This assignment is to augment Program 9 so that the user can interact with a grahics display of the game board:

• The board and the pieces on the board should be displayed in the window. The display should change each time the board is changed by a move, remove, or place command.
• The user should be able to execute the move, remove, and place commands by using the mouse. If you implemented Program 9 so that the user enters commands solely through text boxes, you can leave that feature, but you should also add the capability to use the mouse. For example, the place command could work like this. The program asks for the type of the piece (pawn, king, etc.). The user would then type in the type of the piece, and then click on the square where the piece should be placed. Or you could let the user select the type of the piece by clicking an icon that shows the piece or using a drop down menu. It's up to you; the main criterion is that your program should be understandable and easy to use.

Your program must follow these implementation restrictions:

• Your main method should be in a class named TestChess.
• You must use the Java classes in java.awt and javax.swing to implement your GUI. Some of you may have systems that allow you to "write" GUI programs by using your mouse to create graphics objects, i.e., without writing code. Do not do this. All the code in your program should be text written by you. (Of course, you will need to import and use many Java classes.)
• The program should interact with the user entirely through GUI components such as windows, menus, buttons, text boxes and so forth. The details are up to you; the main criterion is that the commands and responses should be easy to understand and use. The only time the command window is used is to initiate execution of the program.
• All game files should be kept in a folder named GameFiles, which should be in the current directory.
• You should organize your TestChess.java file following the example of HelloWorldSwing in the tutorials. That is, the main method contains nothing but a call to the method SwingUtilities.invokeLater, and the file also contains a static void method which is the start of your GUI code.

Your grade will be based on how well you design and implement the code, how thorough your error handling is, on good programming practices, and on thorough testing. Coding guidelines for Java programs are posted here.

Add comment documentation to your program (all classes) and use javadoc to extract the documentation into an HTML file. Include a javadoc comment for each class and each method. The class comment should include your name and the date (use the @author tag). Method comments should briefly describe the purpose of the method, its arguments, and what, if anything, it returns (using @param and @return as appropriate).

The physical location of the javadoc comments is critical. A class comment must immediately precede the line containing the keyword class, and method comments must immediately precede the method.

When you have commented your source files, run javadoc to create the .html files and view them in a browser of your choice.

You don't need to turn in hardcopy of your source code or test run.

Do not give me a copy of the javadoc.html files.

• All Java programs will be submitted by copying (or ftping) them to a specially designated directory in AFS. Each person in the class has a subdirectory which has the same name as your login in /afs/cu/class/cs242/fa10

  Within this individual directory, create a subdirectory named p10. Copy only the source files and an executable JAR file into this directory, not class files or javadoc files. So, for example, if your login name was smithjd then the files TestChess.java, TestChess.jar, and any other .java files your program uses should be copied to /afs/cu/class/cs242/fa10/smithjd/p10. These directories have permissions set so that no one other than yourself and Prof. Lynch can read the files. You may, of course, use whatever operating system and compiler you wish to develop your code, but the version you turn in, both hardcopy and the files submitted to AFS, must compile and run under JDK installed in the Clarkson ITL (our lab room).

  I should be able to run your program by downloading TestChess.jar into any folder and entering the command line

  java -jar TestChess.jar

• Correct execution. The program must follow all the specifications above.
• Correct implementation. The program must follow all the design requirements above.
• Error checking. You have to figure out what kinds of errors your program should check for, and how it should handle them.
• Readability of the code: commented and well-structured, so that it is clear what the code is doing. Use an accepted programming style. The style of the text is fine, or you can follow the Code Conventions. Whatever you do, be consistent.
• Appearance of the graphics. Your graphics window should be neat and easy to understand.
• Human factors. An inexperienced user should be able to run the program, and the program should interact with the user with clear, understandable prompts and responses. This means that the user will always be able to tell whether or not a command was successfully executed, and if it was not successful, the user is told what the problem was.
• Timely submission of your program. Programs uploaded after the last day of classes (December 3) will not be graded.