what I want is either the GUI knows how to deal wi...

# science

[bjonnh]

what I want is either the GUI knows how to deal with that device and display something like a graphical representation of states etc, or it doesn't know

[altavir]

I've done widgets for boolean state and toggles as well as drop-boxes.

[bjonnh]

yeah that's the advantage of Vue and Vuetify, they all already exist

[bjonnh]

it is really easy to integrate most of them are a one liner

[bjonnh]

you have a model with a JS object (boolean, string, number…) and you just attach it to the widget

[altavir]

Such widgets exist everywhere. But we need to bind it to device, not some property. Also it must be automatically updated on device state change

[bjonnh]

<v-checkbox v-model="mybooleanvalue"/>

[bjonnh]

and your checkbox is reactive to that variable now (both ways in that case)

[bjonnh]

yeah that's why I want that properties abstraction layer

[bjonnh]

I have that for properties now, but not actions

[altavir]

I was using JavaFX property bindings, but even in that case there are some complications. For example, physical states are not updated immediately

[altavir]

Tango has the concept of actions. I DF-controls I've implemented actions as a change of special properties. But it is quite easy to doe standalone actions like fun action(actionName: String, meta: Meta)

[bjonnh]

yep for my measurements I have expected and measured

[bjonnh]

so every property has two states. GUI can work on expected (and tell the user that it is what is expected of that property, not necessarily the real value)

[altavir]

I've hidden internal state and organized synchronization logic to properly update properties on fast change. Probably both approaches are valid.

[bjonnh]

Yeah that's something I was thinking about as well, what to do with ultrafast devices

[bjonnh]

which also makes channels unusable for these

[bjonnh]

you need to make sure something listens

[bjonnh]

and if it isn't fast enough it would just hang

[altavir]

Fast daq is a different matter and requires different solutions. You do not evaluate each incoming value, but accumulate them and produce binary Bunches of data. As for slow listeners, one could use conflated channels or smoothers. Done that as well.