Tristan Ravitch

…odule This is used by both the value viewer and graphviz code. This is non-trivial because, while we can do the mapping based on nonces for many values, we cannot...

The value viewer widget and the graphviz rendering code have no dependencies on surveyor and could be used independently. They can still be posted in this repository.

Terms like `ite` could benefit from having their true/false/condition terms (and edges) marked in different shapes/colors to help visually differentiate parts of formulas.

We have that information easily accessible. It might make sense to make that a dialog or separate view

The inspector allows users to examine the resulting model returned by the symbolic execution engine after simulating a function. Right now, it just prints the result as a string. We...

There should be a command to hide or show the sub-terms of individual (or all) named values. The logic could be a bit tricky, as we don't want to hide...

The `sInputFile` field is not really necessary and no logic should depend on it. We should get rid of it. There are cases where there will be no filename (e.g.,...

After it is possible to assign names to terms (uniquely identified by their nonces), we can render those names next to terms in the `ValueViewer` to help provide some structure...

From the function and block selector widgets, it should be possible to render the call graph and CFG, respectively, to graphviz for easier viewing. For at least the CFG rendering,...

Right now, the "current" object for commands is taken from the context. That could be made more flexible by setting up declarative rules mapping different program modes to data values...