Community Core Vision (Beta)

Tbeta needs a complete restructuring so it can be used as both a standalone application (like it is now) and as a native OF application (addon).

This means, we need to rewrite tbeta so that testapp doesn't hold the main parts of tbeta. This way, people can use tbeta as an addon (by just adding it to their project). A good example is ofxTouch which we could choose to structure similar to if we think it's the right direction.

Restructuring is the most important part right now as almost all features (threading, multi-cam, fiducials, gui) will rely on how we structure tbeta and make it easy to extend in the future.

Possible general class restructuring
-Split test app into several classes. (ie. calibration-process gui, calibration backend (already done?), cpu filters\gpu filters, tracking (already done?), main gui, etc).

Addon
-Then write the code so all we do is need to specify tbeta as an addon in testapp so people can load it. Possibly we should make OSC an example of how to use tbeta as an addon. So the OSC code goes into testapp and we would use this as standalone tbeta (like it is now), but it would also show people how to create a simple OSC based app by using tbeta core addon. This is how touchlib OSC basically works.