Stage{2}@INVESTIGATION: Analyzing the code

[ahinchman1]

Now that TornadoFX-Suite scans code, we'll be using logging to record mappings of associated user inputs and the functions that follows.

[ahinchman1]

• Detect all starting points (programmatic inputs) and recognize possible bounds
• Map out the path of all possible paths

[ahinchman1]

Realistically, I see this mapping best displayed with splayed trees (I think that's the structure). Because most paths are not necessarily linear, it may be helpful to store the possible available permutations in repetition on a file, but the program itself can just store the tree structures in a hash map probably

[ahinchman1]

Update: mapped out node hierarchies. Next stage is parsing out methods to map nodes to methods that change those particular nodes