CMPS 160 -- Programming Assignment 2

Due date:
9am, FRI, 10/16/09

Objectives:

To Do:

• You will be modifying your first programming assignment to add user interaction. You can do this task in stages.
  • Stage 1: (about 10% functionality) In assignment one, you had a fixed position for shooting the projectiles -- the center of the screen. Pretend you have a ``cannon'' at that location. In this assignment, make the following modifications:
    • Create 3 cannons instead of 1.
    • For each cannon, represent each one with a unique color and shape. For example, red circle, blue square, green triangle to represent different cannons.
    • Each time the space bar is pressed, each cannon will randomly fire 1 projectile.
  • Stage 2: (about 30% functionality) Allow the user to click (right mouse down) and drag the selected cannon to a new position (right mouse up). New projectiles will be shot from the new position. Trajectories of projectiles from the old position should be erased.
  • Stage 3: (about 40% functionality) Allow the user to add objects (to act like terrain or obstacles or targets). Previously, the trajectories of the projectiles were traced until they went out of bounds of the screen. This time, allow the user to interactively create objects in the scene. When the projectiles hit these objects, they will stop (ie. you can stop tracing their trajectory).

    Objects are 2D polygons and made by ``rubber banding''. Interactions should be with the left mouse button. A left mouse down action deposits a point (a vertex of the polygon) at the mouse location. Draw a rubber band line between the last vertex entered and the next vertex. The next vertex position will be wherever the left mouse down action is detected. To close the polygon, you need to detect a left mouse double-click action. The first vertex and the last vertex are then connected. This will produce a closed polygon. Specify polygon fill (look up glPolygonMode). Does OpenGL let you have self-intersecting polygons?

    All objects that have been created should be maintained by the program. They are drawn from oldest to most recent, so that the most recent object created can overlap (partially or completely) older objects.

  • Stage 4: (about 10% functionality) Allow the user to move the objects that they've created in the previous stage. Interaction is also done with the right mouse button just like moving the cannons around. Objects can go through other objects while being moved.
  • Stage 5: (about 10% functionality) Allow the user to delete objects (including cannons). Selection is done via the ctrl-click with left mouse button.

  Grading:

  This program nominally accounts for 6% of your final grade. We must be able to compile/test your code. Make sure that the code and accompanying make/project files, etc. are tested for successful compilation at least on the PCs in the lab. Also be sure to include the executable and a README file in your submission as to which platform to use. Programs turned in at least a full day early will earn 1% bonus credit. Late programs will be charged 1% late points. In addition, late programs will not be accepted 24 hours past due date. Late programs and reports will not be accepted for the final project. The bonus credits may be accumulated up to a total of 50% toward program and final project credits. Programs are graded 80% for functionality and correctness and 20% for style, readability, documentation/writeup, and efficiency. Additional points may also be earned for extra features.

  Submission:

  Submission must be done using the "submit" command from CATS.
  • submit cmps160-ap.f09 prog2 prog2.tar, or
  • submit cmps160-ap.f09 prog2 prog2.zip

  This command should work from unix.ic.ucsc.edu. Create and submit a subdirectory called prog2. It should contain the executable and all the files you have to make your program compile/run. Tar or zip up prog2 before submitting.

Last modified Saturday, 03-Oct-2009 14:03:23 PDT.