Open stephanemagnenat opened 7 years ago
The FSM mode for a labyrinth navigation task with optional stop could look like that:
PDF: advanced-mode-rework-paper-prototype_labyrinth-singlethreaded-alt2.pdf
While in this mockup the states are denoted by texts, in the spirit of VPL they should rather be by images. If a program is imported in a state, the corresponding image should be used by default, provided #62 is implemented.
In addition to images documenting the states, it might be interesting for the VPL environment to automatically add a binary code to the state, than will be shown in the LED circle. Then would allow to keep the visibility of the current state on the robot. It would break recursive encapsulation of FSM programs as one state in another FSM programs, so it's a trade-off.
For the sake of clarity for the children, maybe it would be worth describing the different states or modes with different colours that would also be displayed on the robot, for example using the LEDs on the bottom side. These colours could also be visible in the VPL.
Preliminary tests with users show that the current advanced mode prototype does not work, as it fail to impose a clear visual structure and make the notional machine apparent.
In the recent weeks, I have been talking with different people and iterated over a new design.
The result is to provide two editors:
In the state machine editor, for each state one could optionally import existing an program that shall be executed when this state is active.