5 changed files with 16 additions and 0 deletions
@ -0,0 +1,11 @@
|
||||
Although the system has a restricted input-output (I/O) flow from the outside, the internal flow is a bit more flexible. There is still a rigidity to it but it is not as one-dimensional. To help explain, please consider the image below. |
||||
|
||||
INTERFLOW FLOW IMAGE. |
||||
|
||||
How this works is `GridPainter` receives input, usually a record type from `Domain`. From there, `GridPainter` utilises the various functions from the other files to complete the task it received. Because everything runs through`GridPainter`, it doubles up as the libraries co-ordinator. There is (for lack of a better word) no cross-pollination of function calls between the other files. |
||||
|
||||
If you decide to add new features to the library, please try to keep to this flow/structure. |
||||
|
||||
**Note**: The modules listed above are situated in files with the same names -- for example, `GridPainter` resides in "GridPainter.fs", `Domain` resides in "Domain.fs" Etc. |
||||
|
||||
IMAGE OF MODULE TO FILENAME LINKS. |
||||
Loading…
Reference in new issue