Assignment 4 (100 Pts)

In this assignment, you're extending Assignment 3 with the concepts we recently covered--GUIs and Regular Expressions.

Designing a GUI

In Assignment 3, you may have added some basic code to allow the user to enter or edit new Media Items. You will now provide a GUI to allow the user to more easily edit and add items to the library. Note that the library file has a new extension and a slightly different format. The file may not showing up as a text file in the browser. You should save the file (perhaps using "save link as").

Your GUI should allow the user to

• Choose another file to open that contains the library's media items (only files with the .lib extension)
• Print the library's contents
• Sort the items in the library
• Add new items to the library
• Check items in or out of the library
• Save the output file that contains the library in another file (adds the appropriate extension by default)

Design the GUI to be user-friendly, based on the concepts discussed in class and your intuitions for making the program usable. You may want to spend some time looking at the Swing Tutorials or API to make sure that you're using an appropriate component or widget for each part of your interface.

Regular Expressions

In the previous assignment, you read from a file to initialize the library when the program starts up. (Note that the format of the file has changed.) Modify your code to use regular expressions to parse the data file appropriately. (Depending on what you did in Assignment 3, this may require very few changes to your code.)

A driver program

When you execute your program, demonstrate your program's ability to handle strange or incorrect behavior as well.

Packages

Java Docs

README

• Your name
• Assignment name
• Date
• High-level description of the assignment and what your program(s) does
• A list of submitted files
• The online location of your Java Docs
• Instructions for running your program
• Briefly describe how you designed your GUI: How did you make your program easy for users to use? What "unusual" or specialized components did you use and why? How did you write your code to be flexible to changes in the data or GUI?
• Briefly describe the changes you made to your code so that you parse the file using regular expressions. (Rhetorical questions: Was it difficult for you to make these changes? Was your code easy to modify and the changes were localized?)
• Any other information you want Ke or Sara to know

Screen shots

There are mays ways to capture screen shots, depending on what platform/operating system you are running on.

• If you are running on Windows, you can use the PrintScreen key to capture the GUI window to the clipboard. You can copy the image to a desktop publishing app, such as Word, to caption the image and put multiple screen shots on each page.
• If you are developing on a Unix-based system (such as the composers or EECIS machines), you can use a graphics program named XV to capture the GUI window to a GIF image file. To capture using XV, after your program is running and the GUI is displayed, go to the command prompt and start XV using "xv &". (Remember: the ampersand means "run the program in the background, so I can keep using the terminal.") A picture window will open. Right-click the mouse inside this window to open the XV command window. Click the "Grab" button on the lower-right corner, which brings up the XV 'grab' window. Set the delay to something like 5 seconds. Then, click AutoGrab. Then, select your GUI window and left-click in that window, which will capture whatever is in the window. Click the "Save" button, set the image type GIF, specify a filename, and save the image. You need to then view this image using any image viewer or web browser you want and print it.

  After creating the screen shots, you can combine them into a simple HTML page that you can generate and print.

It does not matter how you capture the screen shots. Figure out some way of capturing the image or printing your screen displaying it and make it work. You do not have to use XV or a Unix environment.

If possible, put multiple screen shots on each sheet of paper. Label each screen shot with some context about when the user saw this view. (You can label screen shots either in pen--if neatly written--or in print.)

Submission

Submit a printed version of your assignment--including the screen shots--at the beginning of class on Thursday, July 20.

Electronic Submission Organization

Your submission directory will look something like this:

• sprenkle/
  • assign4/
    • library
      • CD.class
      • CD.java
      • DVD.class
      • DVD.java
      • ...
    • gui
      • ...
    • README
    • docs/ (the HTML documentation)

Email a gzipped tar file of your assignment directory (named lastname, as shown above) to Ke (kli at cis.udel.edu) before next Thursday (July 20) at 11:59:59 p.m. Remember that you do not need the screenshots in your electronic submission.

Please do not submit your code from earlier assignments. You may need to create a temporary location that contains your submission so that you do not submit code from earlier assignments.

If you have any questions about submission, ask early!

Grading (100 pts)

• Correctness (GUI and library classes, driver; regular expression parsing code ): 40 pts
• Ease of use, GUI design: 10 pts
• Organization (inheritance relationships, separation of concerns, good OOP style): 20 pts
• Testing (as demonstrated in screen shots): 15 pts
• Documentation (completeness, correctness, discussion of UI design, regular expressions): 15 pts