- create and setup github account
- create vimeo account (or youtube via google)
- download a screen recording tool
- download and install a development environment
- download and setup openframeworks
- successfully run an openframeworks project, screen record it, and upload to vimeo
- fork class git, and make a pull request to the link of your video on vimeo
- box
- read
Head over to github and create a free account. You may want to additionally install their applications osx or windows. For linux it's command line. On any platform, say yes if it asks about command line git or tools. If you want a student micro plan for private repositories, then ask github edu.
Now to Vimeo and create a free account. Groups you may want to join/follow: OF, eyeo, kinect, resonate
OSX
Do nothing, quicktime has you covered.
Windows (free)
possible option: shadow play
Windows (pay)
Linux
On the openFrameworks page will be instructions for how to download what you need for any platform.
Windows
Don't try to squeeze by with Visual Studio 2017. Unless you know what you're doing, just go get VS 2015.
Download and install OF for your platform and environment; or, if you know what you're doing OF git.
The OF site has help per platform per development environment on how to run a project. If you're using the github repository, then follow the additional directions about how to use get and use the project generator on the OF github page.
Run any project, capture a few seconds of it as proof, and upload that video to your vimeo account. I suggest uploading a standard definition (SD) instead of high definition (HD). We don't need audio on this upload. The free Vimeo account limits your HD uploads, so save them for videos that need it. Vimeo has compression guidelines and tutorials for uploading. Youtube doesn't care so much what you upload.
Fork the Init_00 repository into your account. You may need merge from course repo first, then sync. Enter yourself alphabetically into the links.md file with your name and vimeo link. Create a pull request of the file for your changes to be integrated. There will be merge conflicts that you'll need to resolve.
If you don't already have a box account with RPI, please register for one here http://dotcio.rpi.edu/box
Maeda Creative Code.pdf on Box
Programming Interactivity, Chapter 1, optional
Programming Interactivity, Chapter 2, look through and try to get a feel for what we'll be dealing with when working with code. It's ok to not totally understand it.