Radi is a side project of mine that finally saw the light of day 7 months ago, when I announced it here on HN: http://news.ycombinator.com/item?id=2040844
I've recently tried to pick up the pace with updates to Radi. I'm hoping to finish the first draft of a manual soon, and to get some more concrete examples done. (Producing sample content and tutorials is really hard, because it's not enough to know the app, but you have to be able to see it through the new user's eyes -- very difficult for me when I've worked on the app for so long...)
I'm currently pretty excited about the possibilities of using <canvas> on top of <video>, so that's something I'd like to write some documentation about... If there are any other ideas about topics of interest, I'm all ears!
Oh and p.s. that looks pretty damm good. I do research on visual programming, so I was interested to take a look at your conduit app (reminds me of toolbox) as well. I particularly like the comments you have attached to edges in the graph, sadly I literally thought I'd invented that idea this morning :-)
In other words, it's not entirely out of the question on the long term, but I haven't really done the work to even figure out the difficulty.
Any plans on supporting CoffeeScript?
Radi operates on a lower level to render its animations in HTML. Layers in Radi don't directly become <div> elements in the output; instead, the layer content is rendered either within <canvas> or <video> elements. You can use both together, for example using canvas to overlay some dynamic graphics context on top of a video.
To me, the capability to render content seamlessly to either video or canvas is the most unique thing about Radi. Although I'm still not quite sure how to express that as a benefit to the user, rather than a tech-spec curiosity... :)
(It's possible to do some limited CSS animation in Radi as well. There's a concept called "timeline events" that can be used to animate top-level element properties, so you can also use this model of animation on top of the canvas/video rendering... But it's currently limited to opacity only, so this feature is very much in its infancy.)
It feels like a safer use of my time to work on features, and just aim for a "boring but reasonably professional grey" appearance for the interface. I know that many artists actually prefer grey UIs so that it doesn't compete with the actual content.
I've tried to use Cocoa-native controls wherever possible, and that also limits the UI possibilities quite a bit. The overall look needs to be rather neutral so that changes in the Aqua look don't mess up the custom-drawn controls. (Recently Lion had a big change in most of the standard controls' appearance, but IMHO the updated look made Radi look a bit better.)