Originally Posted by jpollard
You forgot about programmers that have color blindness...
The usual symbol for a test point is a rectangle/square rotated 45 degrees. For loops it was a rectangle with triangles on either side.
And left out a very important concept called "pipe".
Nothing was mentioned about the editor functions - such as simplifying drawing (minimizing line intersections) reoganization (moving chunks of the diagram around). For a basic editor you might look at TGIF.
Nice document for a starting point.
Thanks for your comments.
Colour blindness was actually mentioned in para 4.9 on user configuration. Pipes are shown as thick lines on several diagrams, as are references to stdin, stdout and stderr. A named pipe, however, was not mentioned, and might be a useful addition.
I gave some thought to using a diamond shape for tests, but since any command can have an error exit status it would be just a visual artifact - though it might be useful for documenting the intent and structure of the script.
As for editor functions - that is a good point. I have used GraphViz in the past for automating the layout of diagrams, but I am not sure how easy it would be to use for a complex flow chart. The little program shown in 4.10 already has the capability of moving multiple objects, so manual reorganisation will be possible.
It must be remembered that the intent for this program is simple scripts, not vast complex programs like us programmers tend to end up writing. It must look like it is simple to use.
---------- Post added at 12:40 PM ---------- Previous post was at 12:31 PM ----------
Thanks for the link. I think it makes the case FOR this little project quite well.
Remember, my aim is to build something that a secretary might use to sort some stuff, not to be used by the likes of us to create the next great program.