an empty ofxAddon folder structure for easy creating your own addon for openFrameworks
C++ Makefile
Switch branches/tags
Nothing to show
Failed to load latest commit information.
docs Add docs template. May 20, 2014
example_myFirstExample Incorporate @LeoColomb PR. May 20, 2014
example_mySecondExample Incorporate @LeoColomb PR. May 20, 2014
libs/necessaryLib Remove libsorder makes. May 20, 2014
src Polish/amend the template for a first feedback. Jul 12, 2012
tests Add tests folder for unit tests. May 20, 2014
.appveyor.yml updated appveyor to re-enable 64bits Dec 15, 2016
.gitignore Incorporate @LeoColomb PR. May 20, 2014
.travis.yml travis: refactor to OF scripts Dec 14, 2016 Update READMEs. May 20, 2014 Update READMEs. May 20, 2014 Fixed spelling of License (!Licence) May 22, 2014 Add template. May 20, 2014 case changes and license, removed bin Jul 28, 2012
ofxaddons_thumbnail.png Add ofxaddons_thumbnail template. May 20, 2014


OpenFrameworks addon template for easier development of structurally correct addons.

This template aids you as an addon author in creating an addon in a "proper" way. Doing this enables the openFrameworks community to easily use your addon, and having addons adhere to an established structure makes it easier for the openFrameworks developers to create features around contributed addons, like the addons index at


The template contains all you need to start developing your addon. Download the template using the Download button on the right side of the github page. Unzip, rename and copy it to your addons folder. PLEASE DON'T FORK the addon template repo if you plan on creating your own addon, this will lead to confusion on the Github inheritance/forking graph, and you will unnecessarily have this repository's history in your own git repo.

Further Steps contains instructions and explanations for you. is filled with a template for an informative README file you might want to use with your addon.

Before announcing your addon to the world, you should remove this file ( and the author instructions, and rename to Also, if you have special instructions which people should see when submitting a pull request or open an issue in your addon repository, add a file at the root of your repository. For more details, see

This template reflects the help text found at, and will be updated from time to time by the OF developers.

Thanks for listening, and happy coding!