GUI for mock service

[lukasmittag]

What it has:

• You can add VSS datapoints have a look at them, see when they change and can modify them. (Sliders, checkboxes and entry spaces got used)
• You can add a mock for the VSS datapoints. This includes:
  • Set action or animation action
  • ClockTrigger and EventTrigger(VALUE or ACTUATOR_TARGET)
  • RepeatMode
  • conditions (at least simple ones and like the ones in the example, here I clearly not thought about every possible input and I am not handeling all errors that occur e.g. cast errors) What it has not:
• Dropdown menu where you can search for existing VSS paths in databroker (so you do not have to know what configuration and VSS datapoints databroker uses)
• Not every possible input is yet tested and handled correctly
• works only with databroker
• Documentation

[SebastianSchildt]

Needs some rebasing @lukasmittag

[erikbosch]

I did some sanity testing. I had Databroker running and started GUI service. I then could observe:

• If specifying Vehicle.Speed I could control it (set it), and value was reflected in Databroker
• But if I also set value by kuksa-client then that value will not be updated in GUI, so it seems GUI does not subscribe to updates which maybe is not intended
• I did not fully understood the arguments in the dialog below, what is supposed to happen if I select "read-only" or "mock"

If the behavior I experienced is intended then I have no objection merging, but to simplify for new users I think an example/tutorial with some screenshots would be useful to have in the future

erik@debian4:~/kuksa.val.services/mock_service$ !2024
python showcase_gui/GUI.py
Mock started ...

[lukasmittag]

At least this point

But if I also set value by kuksa-client then that value will not be updated in GUI, so it seems GUI does not subscribe to updates which maybe is not intended

should work that it updates it too. Will take a look again. Adding some screenshots would be definitely good.