search

kaaninan / BAUV-Client

https://hub.docker.com/r/kaaninan/bauv-client
0 stars 0 forks source link

Separate communication (COMMS) tab #21

Closed berkegur closed 1 year ago

berkegur commented 2 years ago

There will be many aspects of the server client comms to monitor and adjust considering that the client will communicate with server through wired or wireless (visible light system) ethernet. In the future, other functionalities may be added.

Therefore, it makes sense to have separate COMMS window to monitor and adjust communication settings and data. I suggest we move the 'Connection' and 'Log' boxes to this new tab. In the future, visible light comms system parameters and monitors can be added to this tab.

A simple 'Connected (GREEN) / Disconnected (RED)' light or icon (to let the operator know the connection is still active during teleoperated navigation or manipulation) may be sufficient in the Navigation and Manipulation tabs.

On the navigation tab, we want the operator to see as little info as possible that is not directly related to the navigation task. The navigation tab should force the operator to focus on the navigation task.

kaaninan commented 1 year ago

We could put the connection icons to separate block (minimal one) or we could put it as a small red or green dot at the top of each block for the corresponding connection status. In what way should we do it?

berkegur commented 1 year ago

Şu aşamada nav ve manip tab'lerinde aynı yerde minimalist bir conn göstergesi olabilir. sadece kısatlma ve tepesinde kırmızı veya yeşil nokta gibi