Skip to main content
Photo by Drya Tryfanava on Unsplash

A2: workstation

Assignment 2 of COMP1720/COMP6720: build an interactive workstation in p5.js that responds to mouse and keyboard input.

In this assignment you will create an interactive workstation in p5.

The world is full of workstations. These can be real (your messy desktop), imagined (spaceship control panels), fun (baby activity centres), serious (air traffic control), creative (painter’s studio), or boring (checkout cash register). All of these workstations have a variety of objects that humans interact with to accomplish some kind of task.

You goal in this assignment is to create some kind of interactive workstation in p5 that’s engaging, coherent, and rewarding to use. The objects in your workstation should fit together in some kind of clear theme. There should be interactive elements in your workstation so that clicking or moving the mouse causes a response in your sketch. You will need to carefully design your interactions and the responses to create an artwork that engages the viewer in interaction and rewards their attention with a deeper understanding or enjoyment.

Outline

Requirements

Your workstation submission must:

And a few “must nots”:

The artist statement

Your submission must include a short (max 200 words) artist statement. This is a short document, written in the first person, which explains:

The artist statement is your chance to tell us what is interesting and artistic about your submission—don’t assume that we can guess. It’s you chance to explain how and why your work is engaging, coherent, and rewarding.

You won’t receive a separate mark for the artist statement, but it will be used to judge how successful your submission is as a work of art and your abilty to design and construct a computer-based artwork.

Getting started

Here’s the process for working on the assignment:

  1. fork & clone the assignment repo

  2. add whatever code you like to make a cool/interesting workstation

  3. when you run the sketch, hitting spacebar will save a still image of the sketch (as a thumbnail.png file in your Downloads folder)

  4. when you’re happy with your thumbnail.png, copy it into your assignment folder (this will overwrite the previous version) and commit the new version to the repo (and push it up to the GitLab server)

Submission process

  1. fork the assignment template repository from the Gitlab server

  2. clone1 & work on your fork of the assignment 1 repo, regularly committing & pushing your changes to the GitLab server

  3. at the submission deadline, the latest commit2 pushed to the GitLab server (not on your local machine!) will count as your submission

Submission checklist

  1. my project satisfies the requirements

  2. my completed assignment has been pushed to the GitLab server, and all the required files (your versions of artist-statement.md, references.md, thumbnail.png and sketch.js) have made it to the server

  3. my references.md file includes at least two references, and everything not mentioned in there is my own work

  4. i have viewed and tested my submission on the test URL and it displays / works correctly

FAQ

Can I change the size of the canvas?

No, you need to use a rectangular 1280 x 800 canvas as set up by the template: createCanvas(1280, 800)

The thumbnail.png has a different resolution than the canvas size - what can I do?

Try adding pixelDensity(1) at the beginning of setup(). See the reference for details and ask on the forums if you need help.

Can I use images or sounds from the internet?

No.

Can I use insert advanced p5 feature here?

Yes, as long as it doesn’t involve using images (see above). We may not be able to help with some advanced p5 and JavaScript that isn’t included in the course so far.

How do I submit my references & artist statement?

The template repo contains “starter” files for both of these. You should change these files to put your own content in there, and commit & push the files up with the rest of your submission.

Basically, everything you need to submit is in that Git repository—as long as you make the changes in there, commit them and push them up to the GitLab server then you’re all good.

Footnotes

  1. make sure you clone your own fork (i.e. the one with your uni ID in the url) to your local machine, not the template (because obviously you aren’t able to change the template for everyone—GitLab won’t let you) ↩

  2. it’s the main branch which counts as your submission—which is the default anyway (if you’ve just followed all the instructions then you’ve been working on the master branch all along) ↩