How does VirtualAwesome relate to OpenFramework

[stefan)]

Since this question keeps coming up I wanted to take some time and
shed some light on it.

The reason why VirtualAwesome feels similar to openFrameworks is
because I and Addie have worked with and contributed to oF quite a bit
and know the community well. In a way va grew out from developing for
oF. In fact the first attempt was to bring OpenSceneGraph to oF in
form of an addon. The reason why it became its own project has a few
reasons. For one osg does very well replace all the graphics stuff in
oF and goes far beyond. Using a scene graph is quite different from
using immediate mode rendering. For two, the coding style of osg it
quite elegant and impressive. Therefore it did not make sense to wrap
it with the coding style of oF. There are also a number of less
decisive reasons like using cmake because it makes cross-platform
development so much more efficient.

Some more factoids:

VirtualAwesome cannot easily be integrated with oF.
The coding style of VirtualAwesome is less oF and C, more
OpenSceneGraph and C++.
VirtualAwesome uses namespaces instead of prefixes.
VirtualAwesome has a similar addons structure as oF.
Addons can be ported relatively easily between va and oF.
va does not try to avoid pointers (because of interface code this is
almost impossible).
va uses cmake for cross platform building.
va core is mostly graphics. Everything else is/will be in addons.
va supports mouse, key, tablet, multitouch out of the box.

Let me know if there are any specific questions,
best,

/stefan