Project 11: Something Interactive
The purpose of the last assignment is to do something fun with your physics engine and user interaction. You can design a simple game or try simulating something interesting.
- Design Your Program
the first task is to design out your program. Your design should contain the following elements.
- Start Screen
The program must have a start screen. This does not have to have any moving parts, but it can. It should tell the user how to begin the main phase of the program.
You can implement a start screen by creating all the elements of your start screen (e.g. text and objects), drawing them, and then waiting for a mouse click. After the mouse click, you can undraw the elements that need to go away and add the elements needed for the main phase.
- Main Phase
The program must have a main phase. The main phase should have some moving parts, respond to user input, and be something interesting. A pinball game would be a simple choice. Asteroids would be a more complex choice, but not too bad. Keeping it simple with very few moving parts is a good idea.
- Final Screen
The program must have a final screen. This does not have to have any moving parts, and it does not have to allow the user to replay the main phase. It can simply exit when the user provides the right input. Ideally, you want to tell the user something about their experience in the main phase, such as a final score.
Submit a picture of your design.
Your design can be a written description, hand-drawn or computer-generated figures, or an algorithmic outline, or some combination. It must be legible and clearly specify what you plan to do and how you plan to do it. As part of your design, indicate how many static and moving obstacles are part of the design and which of those items can collide with one another. Also indicate all user interactions to which the program will respond.
- Start Screen
- Implement Your Design
The second task is to implement your design. Stick with the simulation design patterns we have used so far, such as having objects correspond to classes. If you find it useful to create additional parent and child classes, do so.
As you implement your design, think about places where you can test pieces of your implementation before you have to put lots of things together, any one of which might have bugs.
Submit a screen shot of each phase (start, main, end) to demonstrate you completed this step.
- Test Your Design
The third task is to test out your implementation. For this task, try to partner with someone and test each other's implementations. Discuss how to improve your programs to make them more responsive or interesting or fun.
No one writes perfect code the first time. If you change nothing after someone else uses your program, you aren't listening. Please document at least one change you made in response to feedback in comments at the top of the file you changes.
- Demonstrate Your Design
Show off your work. Have your friends try out your program. Take some screen videos of it in action. Take some still screen shots.
Submit a screen video of your program in action.
Extensions are your opportunity to customize your project, learn something else of interest to you, and improve your grade. The following are some suggested extensions, but you are free to choose your own.
Due to the switch to remote learning, extensions are no longer a graded part of CS 152 for the rest of the semester. They are things you can do on your own to learn more and become better at CS, especially if you are interested in taking more CS courses.
- Make your program replayable so the user can return to the start screen from the final screen and replay the main phase.
- Make your program/game have more than one level.
- Spend time making your program visually interesting. Document this.
- Spend time making your program more fun. Document this and talk about the testing procedure you used (which should probably include other people).
- Two-player. Enough said.
- Simulate a new phenomena such as magnetism, orbital mechanics, or springs and dampers.
- The collision code does not take into account masses. A challenging extension would be to add mass to your objects and then modify the collision code so that when two things collide the velocity changes take into account the masses. (Conservation of momentum, energy, and geometry.)
Submit your code
Turn in your code (all files ending with .py) by putting it in a directory in the Courses server. On the Courses server, you should have access to a directory called CS152, and within that, a directory with your user name. Within this directory is a directory named Private. Files that you put into that private directory you can edit, read, and write, and the professor can edit, read, and write, but no one else. To hand in your code and other materials, create a new directory, such as project6, and then copy your code into the project directory for that week. Please submit only code that you want to be graded.
When submitting your code, double check the following.
- Is your name at the top of each code file?
- Does every function have a comment or docstring specifying what it does?
- Is your handin project directory inside your Private folder on Courses?
If you cannot access Courses for any reason create a zip file with your code and screen shots (not the video) and email it to Prof Maxwell. Please put your name, CS 152, and project 11 in the filename of the zip file. Put your video on Google Drive and submit a link to it on classroom along with your acknowledgements.