Thanks to visit codestin.com
Credit goes to github.com

Skip to content

Replacing/integrating the recipe Web interface #5

@lou1306

Description

@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:

Metadata

Metadata

Assignees

No one assigned

    Labels

    low-priorityIssues that are not crucial and do not have to be addressed straight away.questionFurther information is requested

    Type

    No type
    No fields configured for issues without a type.

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions