Skip to content

Homework Allison

Jump to bottom Edit New page
Allison Parrish edited this page Sep 11, 2019 · 8 revisions

Guidelines

A big part of learning at ITP is learning from each other. So share your work and in exchange you'll get to see everyone else's!

  1. Do the assignment.
  2. Contribute a question.
  3. Post documentation in the form of a blog post. Ideally something visual, some written thoughts, and code. If you are struggling with your sketch and can't get things to work, you should feel free to put your energy into writing about what didn't work (and vent any frustrations!).

E-mail Allison

aparrish@nyu.edu

Allison's in-class examples

I save all of my in-class p5js examples in the web editor. You can see a full list here.

How to turn in your homework assignments

Assignments are due before class begins each week. I will not give credit for assignments that are turned in late. Keeping in mind that I want you to succeed, and that the material can sometimes be challenging, I infinitely prefer inchoate or tentative work to work that is turned in late.

Use this form to turn in your homework assignments.

Scratch document for in-class collaboration

This is a scratch document for in-class collaboration, like sharing links to our sketches, asking questions, etc. I might ask you to add a link to your web editor sketch when we do in-class workshops and exercises.

Week 1: Introduction and drawing

Make sure to set up the following:

Allison's notes:

Assignment

  • Create your own screen drawing: self-portrait, alien, monster, etc. Use 2D primitive shapes – arc(), curve(), ellipse(), line(), point(), quad(), rect(), triangle() – and basic color functions – background(), colorMode(), fill(), noFill(), noStroke(), stroke(). Remember to use createCanvas() to specify the dimensions of your window and wrap all of your code inside a setup() function. Here's a sample example: Elegant Composition
  • Write a blog post about how computation applies to your interests. This could be a subject you've studied, a job you've worked, a personal hobby, or a cause you care about. What projects do you imagine making this term? What projects do you love? (Review and contribute to the ICM Inspiration Wiki page. In the same post (or a new one), document the process of creating your sketches. What pitfalls did you run into? What could you not figure out how to do? How was the experience of using the web editor? Did you post any issues to github?

Resources

Read and watch for next week

Videos listed in Week 2 curriculum outline.

Week 2: Animation, variables

Allison's notes and examples:

Assignment

Create a sketch that includes (all of these):

  • One element controlled by the mouse.
  • One element that changes over time, independently of the mouse.
  • One element that is different every time you run the sketch.

You can choose to build off of your week 1 design, but I might suggest starting over and working with one or two simple shapes in order to emphasize practicing with variables. See if you can eliminate all (or as much as you can) hard-coded numbers from the sketch.

Read and watch for next week

Videos listed in the Week 3 curriculum outline.

Example code:

Week 3: Conditionals

Allison's notes:

Assignment

For this assignment, you'll be working in pairs. Make a rule-based animation that incorporates motion and interaction and includes a user interface element of your own design. Things to try:

  • Make a rollover, a button, or a slider from scratch. Compare your code to the examples in "Examples" below. Later we'll look at how this compare to interface elements we'll get for free from the browser.
  • Create an algorithmic design with simple parameters. Make your interface element control the appearance or behavior of the algorithmic design.
  • When working in teams, try working separately and then combining your work together. Overlay your sketches, or have the interface element you created control your partner's algorithmic design (and vice versa). Trade sketches and riff on your partner's work. Or, sit next to each other at one keyboard and take turns coding while looking over each other's shoulder.

Read and watch for next week

Videos listed in the Week 4 curriculum outline.

Week 4: Repetition with loops

Allison's notes:

Assignment

Create an interactive artwork that implements the concept of repetition with variation. Use at least one for loop.

Inspiration

Read and watch for next week

Videos listed in the Week 5 curriculum outline with links to tutorials, videos and examples.

Week 5: Functions

Allison's notes:

Assignment

Re-work an existing assignment, using functions to compartmentalize your code. Write at least one function that takes parameters and one function that has a return value. If your existing assignments already make use of functions, or if you don't want to build on existing work, feel free to make a new experiment from scratch. Goals and things to try:

  • Break code out of setup() and draw() into functions.
  • Use a function to draw a complex design (like this) multiple times with different arguments.
  • Write a function to that returns the result of a mathematical operation that you need to do several times in your code.
  • Reorganize "groups of variables" into objects.
  • If you are feeling ambitious, try embedding a function into an object.

Read and watch for next week

Videos listed in the Week 6 curriculum outline.

Examples:

Week 6: Objects and arrays

Allison's notes:

Assignment

Arrays and objects allow you to do something new with your programs: keep track of user action over the course of your sketch's execution. For this week's assignment, create a sketch that takes advantage of your new skills. The sketch should allow the user to use clicks, key presses, etc. to add new elements to the scene (and potentially to remove them later). Your sketch should use an array of objects. (Using a constructor function or the class syntax is optional.)

Read and watch for next week

Videos listed in the Week 7 curriculum outline.

Week 7: Document object model (DOM), final projects

Allison's notes:

See also:

Final Project Documentation

It's up to you to figure out how to best document your project, here are some guidelines if you aren't sure what to include.

  • Title
  • Brief written description
  • Visual Documentation: sketch running online, images, video, etc.
  • References: links to related projects, code samples, etc.
  • Source code (please cite your sources in the code comments)
Add a custom footer
Add a custom sidebar
Clone this wiki locally