Earlier quoted context omitted.
there is no obvious convention for visual commands or visual conditionals I don't know about that. Within a particular domain, you can certainly come close to representing these things, or presenting the right controls for a user to represent commands and conditionals. For an example, check out QuickFuse http://quickfuseapps.com Before we built this, we thought about common ways people "drew" voice apps, and commands…
The convention is arbitrary (e.g. most people don't have receivers on their phones and hanging up is done by pressing down a button not by placing the receiver in a horizontal position). If there were an obvious visual convention, the start button would not need to say "start" and the hang up button would not need to say "hang up." That's not to say that arbitrary visual conventions can't have great utility (the alph…
Also, you'll find that that where we departed from conventions for flowcharting, we did it to save pixels, or make the UI more accessible. There is a tradeoff in visual programming between ease of editing and clutter--compare with Max MSP, which has a stark UI, at the cost of having you memorize certain textual commands. If you draw a bare flowchart, it's not obvious how to manipulate it until you draw other GUI controls on top of it or make some modifications. However, it is the general paradigm we are tapping into.