We aim to provide as similar an experience as possible to the real driver station. As such, we need a UI that is functionally identical, and as visually similar as possible to the NI driver station.
Should most likely use the qdarkstyle QT theme (See here)
Should consist of one or more .ui files that are loaded by the app (Feel free to create these with QTCreator or similar, making these by hand is a pain)
Look to QDriverStation for inspiration - They have executed this beautifully. (Note that, initially, we intended to add ROS support to QDriverStation. However, with development winding down with QDriverStation, there's less demand for it at the moment. That fact combined with how much more quickly we can develop in our own repo without having to worry about message definition dependencies and such pushed us to decide to create our own in-house solution, with the intent of hopefully adapting it to work with QDriverStation at a later date. Perhaps as our team grows, we can take over stewardship of QDriverStation and update its communications to get it back up and functional as both a cross-platform NI driver station & a ROS driver station)
One improvement that I would like to see over the real driver station is improved scaling/resizing of the app. This shouldn't be difficult, QT is powerful when used properly. Avoid absolute positioning.
Another deviation from the true driver station will need to come in the form of an additional tab or popup window that allows setting data that is normally passed in from the FMS (ie Event name, match number, etc.)
🚀 Feature Request
Part of #13.
We aim to provide as similar an experience as possible to the real driver station. As such, we need a UI that is functionally identical, and as visually similar as possible to the NI driver station.
.uifiles that are loaded by the app (Feel free to create these with QTCreator or similar, making these by hand is a pain)One improvement that I would like to see over the real driver station is improved scaling/resizing of the app. This shouldn't be difficult, QT is powerful when used properly. Avoid absolute positioning.
Another deviation from the true driver station will need to come in the form of an additional tab or popup window that allows setting data that is normally passed in from the FMS (ie Event name, match number, etc.)