For your last work of this semester, you are to complete the "Lesson Four Project" on page 162 of Shiffman, with the addition of either images or recursive art. Of course, the Lesson Four Project requires completion of Lesson Three (p. 137), which requires completion of the Lesson Two Project (p. 98), which requires Lesson One (p. 42), and then you'll need to incorporate some of what you've learned about image processing and/or the final material in this class on recursion. Yes, you're to do it all!
We'll put it another way. Your job is to construct a program in Processing that is an original work of art. The work should use primitive shapes, lines, color (RGB and/or gray, with or without varying degrees of transparency) and either images or a recursively-generated visual. What you do with this is up to your own vision.
Your work must interact in some way with user input (mouse clicks at a minimum, and perhaps also mouse movement and keyboard input).
At least one aspect of interaction with the user must be affected by a conditional statement (obviously, more than one is fine).
There must be at least one use of a loop (again, that's a minimum number, not a maximum).
Your work should organize significant pieces of code into methods that you define. Definitions of setup(), draw(), keyPressed(), mousePressed(), and other, built-in event handlers are fine (and probably necessary), but they don't count here. You have to define and make use of your own.
Points will be added or deducted, depending on how well you use this kind of abstraction to structure your program. That's a subjective measure, of course, but some guidelines apply almost everywhere:
You must use at least one array, somewhere in your work.
Your work must make use of either images (i.e. the Pimage data type) or recursion (the final topic of the class). You may choose to do both, and will be rewarded accordingly.
Your work will be assessed in part on the elegance and clarity of your code, that is, the clarity an simplicity with which you accomplish complicated tasks. This is a somewhat subjective criterion, but it mainly boils down to the idea that there should be exactly as much code as you need to get a job done, neither more nor less, and what's there should be comprehensible to an independent reader.
As a partial (but not complete list):
Work whose visual presentation reflects a particularly thoughtful attention to grace, detail, and coherence of presentation will count favorably.
Somewhere in your work, there must be a tiny picture of a member of the Felidae family. If this compromises your artistic vision, it need not be present at all times, but it must appear some of the time.
Each file you submit must have a "header" comment of the following form:
/* <file name> ( < n > of < number of files > ) Author: <your name> CPSC 120, Project 3 Last modified: < the date > */
Extra credit may be given for the incorporation of ideas you learn on your own that we have not covered in this class. Examples include effective use of the noise() function (see "Perlin noise"), manipulation of PImage values (above and beyond the basic work we have learned), L-systems, etc. For any such "extra", you should document clearly what idea you have learned and give a clear citation of your source (even if it is page numbers in later chapters of our textbook).
The term "generative art" encompasses more than just interactive visuals constructed by computer programs, though this has become the dominant tool for making such works. Here's a general overview: http://en.wikipedia.org/wiki/Generative_art.
Generative.net (http://generative.net) has a good collection of links to various works
There's a nice (and cheap) book by Matt Pearson that you might enjoy. He keeps a website for it at http://zenbullets.com. Pearson keeps a second gallery at http://abandonedart.org. It's a bit of a time sink, as many of the works are quite mesmerizing.
There is a particularly beautiful work called "Silk", which you'll find at http://weavesilk.com
Submit the folder containing your Processing sketch. This should be a single folder named "project3", which will contain all source code files. Again, the turnin directory is
PLEASE NOTE: Unlike other assignments this semester, you must turn in your own printout of your work, as this best reflects your attention to the presentation of your own work. I will test the electronic submission you make, but I'll only read the paper printout you give me. They should match exactly, of course. Please deliver these either to my mailbox (the Science office, in Eaton Hall) or to my office at Lansing 300.