Assignments:InteractiveArt

From FANG

Introduction

Are video games art? This assignment is about exploring the intersection of video games and art while also learning about various tools in the FANG Engine. In this assignment you can combine your technical and creative skills. You are encouraged to work in pairs on this assignment.

In this assignment your program must not only meet the functionality requirements, but it must also follow the coding conventions described in the instructions below.

Requirements

Your art can be realistic, abstract, fun, scary, or on any range of topics. The only restriction is that your art should be suitable for a general audience (G rated - no violence or sex). You may transform your art into a game, but this is optional. Each of the below parts of the art are 10 points each for a total of 100 points for this assignment.

1. Images - your art should incorporate one or more images. Use ImageSprite for this part.
2. Text - you should include the title of the work and the artist(s) name(s) somewhere on the screen. Use StringSprites for this part.
3. Interaction - the user must be able to interact with the art. The help screen should instruct her/him how to do this. Your interaction should involve some combination of keyboard and mouse.
4. Delayed interaction - some of the interaction needs to take place at least 0.5 seconds after the user moves/clicks the mouse and/or presses the keyboard. This should be done with Alarms.
5. Periodic events - something should happen at semi-regular intervals. This must be separate from the Movement aspect. This should be done with Alarms.
6. Sound - your art should play at least two sounds. When these sounds are played is up to you but they must incorporate panning in some way (play more toward the left or right speaker).
7. Translation - there should be some aspect of the art that continually moves. This should be done with a Tracker.
8. Rotation - there should be some aspect of the art that continually spins. This should be done with a Tracker.
9. Scaling - there should be some aspect of the art that continually gets larger and smaller. This should be done with a Tracker.
10. Help screen - you must tell the user how to interact with your art.

Follow Coding Conventions

In this assignment, your code must be well commented, your methods must be short, and your identifiers must describe their purpose and follow proper naming conventions. You must have an informative Javadoc style comment before every class declaration, field declaration and method declaration. In addition, all method bodies must be 35 lines or less. In addition, you must follow Java naming conventions for identifiers. Class names should start with a capital letter and have each successive word start with uppercase. Method and variable names start with lowercase and each successive word starts with uppercase.

• For every missing or less than informative Javadoc style comment, 2 points will be deducted from your total score.
• 1 point will be deducted for each line past 35 in a method body (i.e. if your method has 40 lines, 5 points will be deducted from your final score).
• 1 point will be deducted for each violation of Java naming conventions.

Be sure to follow the guidelines above because poorly structured code could cause significant point deductions (getting your program to work is not enough - it must also be well structured).