ARTT370: Elements of Digital Media
TECHNICAL EXERCISE 1 - SHAPE
"The computer is a magic box. Many graphic images are hidden inside it. There are geometric diagrams, letters of various shapes and sizes, complex and mutated forms, infinite colors, fantastic plants, beasts and robots, all crammed into hidden corners of the box [...] Shapes like lucky puzzle silhouettes of ancient Egyptian hieroglyphs, instantaneous creations of a kaleidoscope, art deco illustrations, as well as arabesque-like letters, mechanical men and humorous aliens, are all possible."
- Osamu Sato
OBJECTIVE
-Look through The Art of Computer Designing: A Black and White Approach (Sato, 1993) (Links to an external site.).
-Select one full page of the book to reproduce as a single, static processing sketch.
-You must produce the full page. If a page has six small designs on it, attempt all six.
-You do not need to reproduce any text, or any of the black borders on all the pages external to the designs.
My OpenProcessing: https://www.openprocessing.org/sketch/846847
TECHNICAL EXERCISE 2 - TIME.
"The experience of time is highly subjective, as is that of space, and thus the sense of a long moment, a swift day, a fast movie, a slow book requires elasticity in the ways we measure, record and express temporary."
- Joanna Drucker
-Design a clock that tells time without numbers.
-Your clock should be thoughtfully designed and should change based on the hours, minutes and seconds. You may optionally incorporate milliseconds or calendar days.
-Write pseudo code - a “recipe” for your code describing what needs to be done. Convert this to comments in your actual code.
-It does not need to be obvious what time it is, as long as something is changing based on timing parameters.
My OpenProcessing: https://www.openprocessing.org/sketch/851833
TECHNICAL EXERCISE 3 - Input
"In play there is something "at play" which transcends the immediate needs of life and imparts meaning to the action. All play means something."
- Johann Huizinga, Homo Ludens
OBJECTIVE
-Design a 1-button game.
-Your game should use only one form of input (one keyboard button, mouse click, etc).
-Write pseudo code.
-It does not need to have a win or lose condition. There should be some kind of goal or purpose for the player.
-Your game should use only one form of input (one keyboard button, mouse click, etc).
-Write pseudo code.
-It does not need to have a win or lose condition. There should be some kind of goal or purpose for the player.
**For example, you could build a tool that designs cakes, or an interface for "paper" dolls.
