Watch Page for multiple operators

[WilliamsJack]

Is your feature request related to a problem? Please describe. If a second instance of the SIGHTSInterface is opened on another device, the original instance is disabled. This is done to ensure the robot is only receiving instructions from one individual at any given time. This may be disadvantageous to multi-operator setups, where one individual is controlling the robot while other operators are analysing sensors or monitoring hardware.

Describe the solution you'd like A watch page available at http://hostname/watch could provide these individuals with access to cameras, sensor data, logs and SSH terminals for analysis and monitoring on their own devices without giving unnecessary access to robot controls and configuration.

Describe alternatives you've considered An alternative is to allow multiple operators on the main page and let end-users manage their teams correctly to ensure the robot does not receive instructions from multiple devices.

[Conr86]

I think this issue should be approached once #45 is complete. That would likely be the last major change to the interface's functionality and layout, and so would be a safe time to create the watch page.

Likely, all we'll have to do is duplicate the main index.html to a watch/ subdirectory, and modify the HTML file to remove the following GUI elements:

• config editor
• ssh window
• gamepad connection indicator
• drive speed modifier buttons
• service controls
• config file selector
• power buttons

And also removing the following script references from the HTML file:

• sights.config.schema.js
• sights.control.js
• sights.demo.js
• sights.ssh.js
• sights.supervisor.js
• gamepad.min.js
• highlight.pack.js
• json-editor.js
• js-yaml.js
• keyboard.min.js