Schedule
- Introductions, due by the end of the day Thursday, September 6
- Transforming Images, due by the end of the day Thursday, September 6
- Screen Savers, due by the end of the day Saturday, September 22
- Pixmap, due by the end of the day Tuesday, October 30
- Recursive Art, due by the end of the day Sunday, November 18
- Arkanoid (Extra Credit), due by the end of the day Thursday, November 29
- SLogo, due by the end of the day Thursday, December 6
Starter Code
Most assignments will include code to get you started. This may consist of completed classes that you will utilize but not modify or classes in which some methods have been completed and others are left for you to fill in. In either case, comments will clearly indicate which sections of the code you may edit and which must not be modified (you can go to these sections directly by using the Tasks view within Eclipse). All starter code may be obtained with the Ambient download tool by following the directions here. The download site for the course is
http://www.cs.duke.edu/courses/cps006/fall07/snarf/
Assignment Submission
All assignments must be turned in on the due date given; if your assignment is received after midnight (i.e., the next day), it is considered late. You are responsible for ensuring that all files are turned in on time, if a program is turned in late there is a penalty detailed online here.
When you are done with your project and are confident it is satisfactory, you should submit it electronically using the directions available here. You may submit an assignment as many times as necessary, but only the files included in the last submission will be graded. Thus, you should always submit all your project's files -- even if they have not changed since a previous submission. Note, an assignment is considered late if any submission is late, even if your first submission is on time. You may lose points on your assignment if your final submission is incomplete or late.
README Guidelines
Every assignment submission must include a plain text file, named README or README.txt (please use all capital letters in naming the file), that includes the following information:
- Your name
- The date you started the assignment, the date you completed the assignment, and an estimate of the number of hours you worked on it
- A list of the students with whom you discussed the assignment. Since assignments are to be your own work, you should keep track of anyone with whom you have had a significant conversation about a program. You are welcome to talk with the course staff about the assignment, and to other students about broad ideas and concepts.
- Note any books, papers, or online resources that you used in developing your solution
- There may also be specific questions given in the assignment whose answers you will be asked include in this file
- You may include your impressions of the assignment to help the course staff improve it in the future.
You may lose points on your assignment if it does not include a proper README file.
Within Eclipse, you can create plain text file by choosing File -> New -> Untitled Text File.
Code Style
Finally, note that a significant portion of your assignment grade is based on the readability of your program. This readability grade includes style, comments, and the naming of variables and methods.
You must include a comment at the top of each source file you modify that includes your name, course and purpose of the class specified. For example:
// Name: YOUR NAME HERE // Course: CompSci 6 // // Purpose: // PURPOSE OF CLASS HERE
