This looks awesome. I find the problem with visual programming is that often there is multiple representations or diagrams that would be useful to combine and

This looks awesome. I find the problem with visual programming is that often there is multiple representations or diagrams that would be useful to combine and render into a program. * A box and line diagram with arrows is enough for representing event handlers and event dispatchers and message queues automatically. * There's multiple approaches or methods to think of a computation: pipeline, communication, mathematic operations, projection. Each of these can be visualised. * Behaviour composition - how do you combine behaviours together visually? Too many things on the screen and the underlying insight to the problem becomes hard to see or notice. I'm working on a representation of code that is visual but it's not traditional. https://github.com/samsquire/structural-visualization https://github.com/samsquire/structural-visualization