FHTW Berlin Fachbereich 4 Internationale Medieninformatik PROG1: Programmierung I Wintersemester 03/04

---

Laboratory 13: Scribbler

In lab, you should write and test the code that you designed for Lab 12.

As always, you should implement your code in simple, testable stages, building on your code only as each stage works robustly. In this case, it should be as simple as following your development plan.

A few notes:

When you write the initial test class, you will find that it doesn't really exercise the drawing area. You may want to try overriding the drawing area by extending SmartCanvas and overriding its paint method. For example, you could make it draw your Japanese flag (from the finger exercises).

When you are writing your event handler(s) for SmartCanvas, you may wish to begin by drawing dots wherever the mouse is clicked. You can also try drawing straight lines (from where you press the mouse to where you release it) as a simpler case before handling full-blown scribbling.

If you have completed a Scribbler that responds to (some) mouse events, you have accomplished the basic (target) desired functionality.

Additional (Bonus) Functionality

You don't need to go beyond building a working line-drawing Scribbler. However, there are lots of bells and whistles that you can explore if you are so inclined. These include more sophisticated event handling, connecting the Choice and Button components, or even adding additional widgets of your own. One caveat: we recommend that you stay away from modifying ScribbleData. (We do, however, strongly recommend that you use ScribbleData.)

A useful method that you might want to use if you reach this stage in your program is:

• public java.awt.Color cs101.util.Coerce.StringtoColor( String );

In your report

At a minimum, your report should explain how your code handles mouse events in the drawing panel, ideally by drawing the appropriate lines. If your code does not behave as expected, you should explain why or describe what you have done to try to figure out why.

If your code does more than draw lines, you should describe and demonstrate what it does as well as how you were able to achieve this behavior.

It is always more important that you write clean, modular, well-documented and easy-to-understand code than that you go on to advanced features.

Post-Lab, AKA What To Turn In

Your completed assignment should include:

• your pre-lab assignment, including the finger exercises.
• your development plan, along with a description of how (if at all) it corresponds to what you actually did in lab.
• your code and a description of its functionality.
• documentation of your code. (This can be inside the code.)
• your observations concerning
  • the coding/debugging process,
  • the behavior and reliability of your code.
• the names and roles of any collaborators in any parts of the project.