just wanted to give some heads up and info about addons. they have presented a real challenge, but we think we have a good solution and we will release it soon.
To clarify, an addon is some additional code / libraries that extend openframeworks and add additional functionality. It will be a way of adding in support for different types of functionality which is not necessarily included in the core OF code, such as opencv, network, OSC, midi, shaders, etc.
Our goal in the future is to make this as simple as possible, because this is one of the harder parts of working with C++ / compilers: adding code and libraries to a project. The solution we have will work and may lend itself to automation. The other goal is to make these addons easy to update and support.
So here are some features of the new addon approach, and some info about it :
all addons will be just one folder for all compilers / platforms
the folder will contain an xml file called “install.xml” that contains human readable / machine readable info about steps for installing
users will have to install the addon to the OF directory (basically copying the addon in, and putting some code in ofAddons.h. Users will then add that addon per project that they want to use it in
starting with OF 0.05 we will release OF core and OF fat. the core will be the same as before - core OF and examples. OF fat will include most common addons (opencv, network, etc) and examples of their usage, also one mega example that includes them all just to check for incompatibilities etc
to give some indication of what it will look like, here are some screen shots. we’ve done mac, windows and are just working on linux so it should be really soon.
what the addon folder will look like
each addon folder includes src, install.xml and necesssary libs, etc
also, the addon will have everything needed for all platforms and compilers While at first, an addon might not support all targets, we hope over time different folks will help with that support. We will try to post guides about porting addons, etc.
a look at the install.xml file
The xml should be an instruction set of how to install for the OF folder and for the specific project you want.
how to use an addon, once it’s been installed to the OF folder and to the projectit works from #define – you say what you want to use and the addons.h does the work of getting the addon loaded, via code like this:
//-------------------------------------------- ofthread #ifdef USING_ADDON_OFTHREAD #include "ofThread.h" #endif
To compliment the addons, we are also developing a new website on a different host (we are currently on dreamhost and they are http://digg.com/tech-news/Dreamhost-mistakenly-bills-customers-for-multiple-years">terrible)
. that website will use drupal / projects (like : jquery.com) in order to allow folks to upload and maintain their own addons, etc.
So - that’s where we are heading. We would love feedback, and we hope to have this really soon. Thanks as always for the patience and support.
over n’ out -