A while back I started to work on cleaning up the departures app since it seems a lot of the things in the code (and UI) is legacy from T-Skylt when the product only had subway status and no global state or view. However I dropped the ball but when I saw #17 I was thinking about mentioning it in the PR but didn't manage before it was merged.
First of all, I want to ask if there are any products still out there that doesn't run the MatrixBOX system but still uses this app code, i.e. do we need to keep these things in the app for legacy purposes? If not, the things that I think would be nice to fix are
Settings and UI elements that now live (or should live) in the global settings view
Likely dead or duplicate
UI/UX related
Future improvements
I've started to work on this and am trying to tear pieces out one-by-one and confirming it still works as expected and I'll happily continue to explore this if you agree on the issue and thing the checklist looks sensible?
A while back I started to work on cleaning up the departures app since it seems a lot of the things in the code (and UI) is legacy from T-Skylt when the product only had subway status and no global state or view. However I dropped the ball but when I saw #17 I was thinking about mentioning it in the PR but didn't manage before it was merged.
First of all, I want to ask if there are any products still out there that doesn't run the MatrixBOX system but still uses this app code, i.e. do we need to keep these things in the app for legacy purposes? If not, the things that I think would be nice to fix are
Settings and UI elements that now live (or should live) in the global settings view
start_ap()and stops/restarts the system's hotspot itselffunctions.scan()(network scan for the SSID dropdown) and the/checknetroutemkhtml()Likely dead or duplicate
Boot/connect splash "logo" - shown while the app is doing its own WiFi connect flow. The system already hasshow_logo()/logo_anim_step()inmain.pyfor exactly this moment. Removing the app's own WiFi flow removes this by extension.UI/UX related
Future improvements
I've started to work on this and am trying to tear pieces out one-by-one and confirming it still works as expected and I'll happily continue to explore this if you agree on the issue and thing the checklist looks sensible?