Show Posts
This section allows you to view all posts made by this member. Note that you can only see posts made in areas you currently have access to.
Congrats guys! You're going to be reading for a while
): 
HOW'S ORGANIZED THE SCRIPT
Since this is a rather complex script, a precise design of subs is necessary.
The script moves on various levels. The upper levels know and use the lower ones, but not vice-versa.
Each function is identified by a prefix, which indicates the level of membership.
You can pretend that they are like packages in Java.
LEVELS:
1 - Elementary functions (prefix: Std)
There are subs who are carrying out tasks simple and basic, with no dependencies on other subs.
It is generally "low level", "reusable", "reentrant" (do not depend on global variables)
2 - logic functions (prefix: Model)
Implement the logic of the script, regardless of configuration problems or the like.
Obeys a "design by contract" logic: claiming pre-conditions guaranteeing post-conditions.
Generally depend on some global variables.
They are the "model" in Model-View-Controller architecture.
3 - GRAPHIC FUNCTIONS (prefix: View)
Create the menu and run the loop.
[...]
4 - executive function (prefix: Ctrl)
They are the link between the GUI and the functions of logic level.
They often have similar names corresponding to the functions of the logic level, but they are on a higher level.
In fact, they require certain parameters from the user if needed, and are involved in the loop start process.
You can think of them as "Whatever that happens when you press a button."
This represents the "controller" in Model-View-Controller architecture.
