Pinned Loading

1. Git Guidelines Git Guidelines

   1

   ## Git Guidelines

   2

   * This project uses the GitFlow workflow as described [here](https://www.atlassian.com/git/tutorials/comparing-workflows/gitflow-workflow) and [here](http://nvie.com/posts/a-successful-git-branching-model/). In short, this means that there are two main branches, `master` and `develop`. As the name suggest, the `develop` branch contains code that is under development and `master` contains that is in production. In addition, every feature that is being developed has to be in their own respective branches, this is necessary for separation and makes it easier to solve merge conflicts. Once a feature is ready, it will first be merged with the `develop` branch and once enough features are in `develop` they will be moved to the `master` branch.

   3

   * The Git commit messages in this project should follow the Seven Rules as laid out by Chris Beams, the article can be found [here](http://chris.beams.io/posts/git-commit/).

   4

   * Every release of the app should be tagged using the tagging feature of Git, you can read more about it [here](https://git-scm.com/book/en/v2/Git-Basics-Tagging). It allows for easy separation and is also part of the GitFlow workflow. An example: `git tag -a 1.0 -m "Version 1.0"`.

   5

   * Version tags should follow "Samantic Versioning 2.0.0" pattern. More info [here](https://semver.org).

2. Tone generator in processing Tone generator in processing

   1

   import processing.sound.*;

   2

   3

   // Oscillator and envelope 

   4

   TriOsc triOsc;

   5

   Env env; 

3. lastgraph lastgraph Public

   Forked from andrewgodwin/lastgraph

   Archived code for LastGraph

   Python

4. openFrameworks openFrameworks Public

   Forked from openframeworks/openFrameworks

   OpenFrameworks is a cross platform open source toolkit for creative coding in C++.

   C