Draw a face using at least 10 graphic elements. Experiment with the use of at least 2 colors in addition to the background. For an extra bonus, use curves.
Starting from the provided framework
, make an image (face or other) that responds to the microphone activity.
(Note: Please be aware that, due to restrictions in your browser, these applets can only work when downloaded to a locally-executed copy on your own computer.)
Put your hello world here
Create a composition with 12 randomly generated shapes, using iteration.
Create a composition which generates a pattern of tiling wallpaper.
Make a composition which depicts “order” when the mouseX is on the left side of the canvas, and “chaos” when it is on the right side. The degree of order/chaos (entropy) should vary smoothly with the position of the mouse.
// 10 points:
// 6 points: A 10x10 grid of down-pointing isosceles triangles are drawn.
// 2 points: A single variable controls the size and spacing of the triangles;
// they are exactly as tall as they are wide, and they are spaced at intervals
// equal to one-and-a-half times their width.
// 2 points: Each row of triangles is a darker and darker gray;
// The top row is exactly white, and the bottom row is exactly black.
Design a graphical totem/emblem/figure. It could be a character, person, car, etcetera. Let’s call this your “rubberstamp”. Then implement the following function, which draws the totem (rubberstamp) at the location specified by the arguments, px,py. Your function should also accept at least one parametric “knob” (called controlParam) that modulates the appearance of the stamp somehow (perhaps its color, size, number of gills, etcetera). Give your control parameter a good name.
Call your function three times, to produce a composition with three of your rubberstamps. Upload your project to the OpenProcessing classroom.
Use two for() loops, to create a function in which your rubberstamp is placed in a grid. Add some random variation using your control parameter(s).
In an interactive program with no background() call, create an interaction in which your rubberstamp is placed wherever the user clicks. Use your rubberstamp function to allow the user to place copies of your emblem around the canvas by clicking the mouse. Upload your project to the OpenProcessing classroom.
Visit “Painting with Interactive Pixels” (http://www.idi.ntnu.no/~dags/pip.html) by Dag Svanaes. (Caution, this applet is very old (1997!) and may not work properly in some browsers.) In a single interactive applet with a gray background, create ten square “buttons”. In these ten regions, implement all ten of Dag’s interactive paint types. Observe how several of his paints are irreversible, while others are reversible. Label your buttons using Dag’s icons.
Extra Credit 1. Use circles instead of squares. Only clicks inside the circle should have an effect.
Extra Credit 2. Implement a general point-in-polygon test, and make unusually shaped buttons.
Make a fuse onscreen that takes exactly 5 seconds to complete its timer. At the end of the timed 5 seconds, trigger an interesting event — like, you know, fireworks. Does it have to be a “fuse”? No, it could be a progress bar, or an ice cube melting, or a balloon inflating, or something. Does it have to be fireworks? No, it could be a gun showing the word ‘Bang’, or a balloon popping, or a volcano erupting, etcetera.
Extra Credit. Use an array (which we haven’t yet covered in class) to create a group of objects whose movements are triggered by the event. For example, particles in a fireworks display.
In 2007, Steph Thirion developed a 'six hour long workshop with the objective of showing the participants that it is not required to understand code to experiment and play with it. [...] Although they had no experience in coding, the task of each participant was to make a mod (modified version)' of a Breakout game written in Processing. Now it's your turn: Make it yours! Add, remove, or modify anything you please. It does not need to still be a game when you’re done.
Steph’s Breakout source code is here:
Make a “visual clock”. It is not essential that the time of day be literally readable from it, but your clock should appear different at all times of the day, and it should repeat its appearance every 24 hours. (You can make a 12-hour clock if you prefer). If you do decide to make the time literally readable (e.g. by counting graphic elements, visualizing numeric bit patterns, etc.), you are not permitted to use conventional Roman/Arabic/Chinese etc. numerals.
Make a puppet with limbs. Give it a dynamic behavior; you might find it helpful to use the noise() function.