Thank you for translating. I have been using google chrome right click "Translate to..." to read this forum so far.
Here is an image mock up using draw.io to illustrate one style of encoding additional helpful information into diagrams, on second thought all it would need are image prefixes for certain things, like here there is a gear icon to indicate something is a diagram or function name, and a blue circle to indicate the parameter named n should be a number. The images used are not neccesarily that important, as long as they are consistent, they will be quickly learned by users.
In programming text editors, there is often an autocomplete feature which previews the name of the parameters of a function as you type. One exciting advantage to this feature and diagrams is that such an autocomplete in Drakon could preview not only the name of parameters, but the type icons, as you are writing a function call in a diagram.
To say it another way, Drakon revolutionized coding because it exposes the control flow of programs in a visual way which increases clarity. By giving variable types visual cues, the same process is repeated to give added clarity to programming workflows. Another area to explore this would be tabular data such as large objects stored in variables, akin to database records or spreadsheet data. A visual table in a diagram might be a better option than whatever the programming language syntax is. Each cell in a table could be displayed in a friendlier visual way than ASCII syntax like {} from Lua or "key:value" from JSON.
Here's another example to illustrate creating a wizard unit for a specific team number in a game. A new icon is introduced "pink diamond" to signify a string type variable, and a table is used to create the unit variable (associative array) rather than code syntax.
See the drawing in the next post.
