Replacing/integrating the recipe Web interface

[lou1306]

The question here is: how do we replicate the features of the current Web interface within the "boundaries" of a VS Code interface?

Some ideas:

• The "easiest" way would be to define a bunch of Commands and Tasks. These pop up in the command palette and/or when the user wants to "build" their file.
• Temporal specifications could also be integrated with the Test pane, at some point.
• The main issue is how to replicate the interpreter features. Maybe by integrating with the VSCode debugger, but then how do we deal with nondeterministic choices? How do we present a trace? (This also relates to model checking, as we need to display counterexamples)

---

Resources:

• Commands: https://code.visualstudio.com/api/extension-guides/command
• Tasks: https://code.visualstudio.com/api/extension-guides/task-provider
• Tests: https://code.visualstudio.com/api/extension-guides/testing

[lou1306]

Making inroads into this:

• recipe is now a submodule of this repo (d895575)
• The Makefile contains instructions to build the jar file and place it in the bin directory so it will be bundled with the extension (7374b0a)