Closed podhrmic closed 3 years ago
For now, I could just rely on triggering a javascript alert() which is a modal dialog.
On Wed, Jun 9, 2021, at 1:24 PM, Daniel M. Zimmerman wrote:
@.**** commented on this pull request.
In besspin/cyberPhys/specs/state_machine_hacker_kiosk.txt https://github.com/GaloisInc/BESSPIN-Tool-Suite/pull/1192#discussion_r648659225:
- state "Hack infotainment" as ScenarioBaselineHackInfotainment
- ScenarioBaselineHackInfotainment: show available infotainment hacks +Slide6_A --> Slide6_B: "OtaHack.hackServer()" returned True
I think that's fine as far as it goes... but it's not clear what the UI should do in the event of a failure. We can't really just move on to the infotainment hack screen.
— You are receiving this because your review was requested. Reply to this email directly, view it on GitHub https://github.com/GaloisInc/BESSPIN-Tool-Suite/pull/1192#discussion_r648659225, or unsubscribe https://github.com/notifications/unsubscribe-auth/AAAOZBFKM4CVE4QT7BFSXRLTR7EYNANCNFSM46IKVGFA.
For now, I could just rely on triggering a javascript alert() which is a modal dialog.
Sounds reasonable.
Creates a state machine reflecting the kiosk slides, and describing the actions needed to happen at each state (important for the Python backend).
Rendering here:![state_machine_hacker_kiosk](https://user-images.githubusercontent.com/2790461/121077437-79569b80-c78c-11eb-9a7a-7b34021ee8af.png)