akloeckner

> > > @akloeckner I've noticed that in every modular popup we are merging a dummy object with tile defaults. Why don't we have simply assume the defaults if certain...

> > > For most users `false` would probably same as `undefined` :) I'd beg to differ: * For the user, `fullscreen === undefined` means that they don't set the...

> But that also means that it would not be possible to remove a property completely We could agree on a general perspective for that. So, maybe `null` or `undefined`...

> We could probably define those defaults in a variable and reuse it? Sure! I could do that in the next PR on the camera popup. I would move those...

I have something similar for my "radio". It's an input select + two scripts to start and stop the radio. All of this looks nice in TileBoard too. If you...

> I think it would make sense to support function at the `tile.list` level also. We could make `getItemFieldValue` call `parseFieldValue` not only on the last found value, but on...

Might be related, or not: I have a sensor that changes frequently. I noticed that, when I re-open the browser after minimizing it, the sensor replays multiple values very quickly...

Another idea (under the same disclaimer), we could maybe `debounce` the updating of the view after each incoming state change. That way, all state changes should be updated at once....

Can't we play sounds natively in JS? If so, it could be done by redefining the default actions. A bit messy to configure, I admit...

Possible duplicate of #443, just from Germany this time? And it seems to work again...