Preview: VVVV-to-VVVV.js Connection

Watch this preview video on youtube to get an idea of how you will be able to connect VVVV.js to VVVV, and finally get the runtime-patching experience we love VVVV for.

Release: more Canvas with v0.1.2-alpha

With slight delay we finally reached the next milestone with version 0.1.2-alpha. Besides some changes under the hood (mostly regarding graph evaluation), this release introduces a bunch of new nodes, covering a major part of Canvas 2D drawing functionality. As a development guidline we used this handy Canvas HTML5 Cheat Sheet.

Version 0.1.2-alpha allows us to:

• draw vector shapes like bezier curves, arcs, rectangles, text
• fill them — solid or using gradients
• stroke them, using several stroke styles
• draw images and streaming video
• render shadows and glows
• use various blend techniques
• transform all this using regular VVVV transform nodes

Have a look at the CHANGELOG, and check out the Examples here, to get the details.

Thanks to vux, defetto, matise and micro.d for contributing to this release! The next big step is tackling the WebGL pipeline, by implementing dynamic shaders, render state nodes, etc. If you're interested in participating here, contact us via Github!

Also, we set up a very basic out-of-the-box Forum, to provide you with a place for questions and suggestions. It's brandnew, so don't be shy!

VVVV.js' road to 1.0

Many of you might wonder how this VVVV.js thing is going to evolve, and when it will be actually usable, if at all. So probably it's time to create a rough plan with some milestones, that have to be accomplished.

Of course, the roadmap below is not carved in stone at all. Rather, it's an overview of the things that have to be tackled, and of when this might happen.

As you can see, we're first heading for some visual bragging to find out, what's possible in terms of Canvas 2D and WebGL 3D graphics (In fact, the set of Canvas drawing nodes will be released this week).

After this, we will deal with ways to connect VVVV to the browser, to simplify the development process, and create the VVVV-typical patch-while-running experience. Simultaneiously, lots of the many utility nodes should be ported at this stage, beginning with String and Value nodes, to pave the way for some data visualization demos.

Other steps include handling subpatches, getting rid of VVVViewer glitches and of course performance optimization.

As you can see, there's a bunch of work to do, and we could really use some help. If you're interested in any particular component, get in touch with us!