The dictionary, such as it is, is in the Glossary section of the user manual section.
If there is items missing, feel free to point them out, then I could add them when I think of it - or not, which is fine.
That may be, but the loop names have been defined for decades.
See Wikipedia, Structured Programming, specifically:
- "Sequence"; ordered statements or subroutines executed in sequence.
- "Selection"; one or a number of statements is executed depending on the state of the program. This is usually expressed with keywords such as
if..then..else..endif
.
- "Iteration"; a statement or block is executed until the program reaches a certain state, or operations have been applied to every element of a collection. This is usually expressed with keywords such as
while
, repeat
, for
or do..until
. Often it is recommended that each loop should only have one entry point (and in the original structural programming, also only one exit point, and a few languages enforce this).
As you can see, these are the same elements that Keyboard Maestro uses:
The same elements I used when I programmed Pascal. More or less the same elements used in C and all its derivatives.
I'm afraid if you don't like the terminology you will require a time machine to go back and visit Dijkstra some time in the early 60s, and have a chat with him about his naming choices.
Although in any event, the While loop does what it says: While the condition is true, execute the actions. Now you can nitpick and say, “hang on, if the condition becomes false half way through the execution of the actions, why don't they stop executing”, but that is not how it works - consider both the condition and the actions to be atomic indivisible chunks of code as far as this behaviour is concerned. While the condition is true, execute all of the actions, then check the condition again.
There is no question the documentation could be different, the terminology could be different, the design could be different, etc - but no documentation will satisfy everyone, no terminology will make sense to everyone, no design will be optimal for everyone. That's life, it is full of history and compromises.
In any event, yes, there is a glossary, and if anyone wants to suggest additions, they are free to do so, or not, because no one, other than me, is actually paid to improve Keyboard Maestro, and so no one, other than me, has any obligation to do anything.
I'm happy to lock this topic if it is not going to be constructive.