You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on May 12, 2020. It is now read-only.
The system should be able to run perfectly without any of the human interface devices (LCD, RFID, buttons) being available. That is, the admin UI should function great for controlling mpd. This is the typical setup during development.
The system should function with only some HIDs present. For example only the buttons, or buttons and RFID, etc.
The system should function with the admin UI being down. That is, be able to shut down the Phoenix app and the buttons and RFID can still control music playback
So then, the only app that is truly required is the music player itself. In other words, all HIDs and the admin UI depend on the music player, but the music player shouldn't depend on anything else.
So, how to we structure the app so the HIDs and UI can easily talk to the music player and be made aware of events?
Here's a basic sequence diagram of how the parts interact with the player. Since the LCD is read-only, it's not included. It would just listen for events.
Issues
The HIDs won't compile on a system that doesn't have SPI or GPIO available.
The text was updated successfully, but these errors were encountered:
Sign up for freeto subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Goals
So then, the only app that is truly required is the music player itself. In other words, all HIDs and the admin UI depend on the music player, but the music player shouldn't depend on anything else.
So, how to we structure the app so the HIDs and UI can easily talk to the music player and be made aware of events?
Here's a basic sequence diagram of how the parts interact with the player. Since the LCD is read-only, it's not included. It would just listen for events.
Issues
The text was updated successfully, but these errors were encountered: