I like how it says "Your drawing looks good". Why doesn't gcc ever compliment my code?
It was painful.
I think it would be much easier to edit some textual representation, and then use a program to convert it to the graphical one, if you want to read it this way.
I like to think of graphical programming languages as DSL's: when they're aimed at the right problem, they're like a hot knife through butter compared to a general purpose tool. But when you start using DSL's for things in which they are not intended you end up with nightmarishly obscure codebases.
But seriously, these look just like the flowcharts that were all over CS in the seventies. And the code that's generated (based on the examples from edent and dchest) is basically unmaintainable GOTO-hell that looks like what you get from decompiling code without symbols...
I'd be curious to see what gets generated for the parallelism stuff, tho.
This actually looks useful -- the simple set of rules they suggest make a lot of sense for general flowchart readability, and these could be easily shared with business partners of only a half-technical mindset.
I was curious how you would handle event driven architectures with it, however -- or is that outside the intended scope?
Once drawing becomes more productive (which I don't see exactly how, to be honest) then diagram-based languages will raise their heads. Until then, no, thank you.
A well established one for kids & novices is Scratch: http://scratch.mit.edu/
The .drn file format is a SQLite database but it looks like it encodes the coordinates of the elements directly rather than storing symbolic relationships and doing a layout. If you could use a Graphviz-like language to describe the diagrams but add the Drakon rules for structure and layout (and presentation) I'd be a lot more enthusiastic.
I remember putting in around 30 hours on a consulting project trying to use ObjectVision 2.1 (I think that was the version - been a while) before finally giving up and going to FoxPro in disgust... Had to keep project deadlines.
Nearly anyone should be able to understand a flowchart and also make improvements and understand why that feature is more or less difficult to implement.
I know this isnt new, but really liked it