jamulussoftware / jamulussoftware/jamulus
Audio alerts: Consider JSON-RPC use case
Open
feature request
JSON-RPC
- Dominant language
- C
- Stars
- 1.1k
- Forks
- 248
- Avg merge
- 2d 3h
- Merged PRs (30d)
- 9
Description
> One other fundmental issue I have with the approach is that it's adding non-visual code to ClientDlg. That shouldn't happen. Why would I not want the audio alerts if I were using the JSON RPC client without the graphic UI?
_Originally posted by @pljones in https://github.com/jamulussoftware/jamulus/issues/2640#issuecomment-1172632352_
Contributor guide
Research direction
Start by reviewing ClientDlg and the JSON-RPC client context mentioned in the issue. Clarify how audio alerts should work without the graphical UI and where that behavior belongs; the work is done when the JSON-RPC use case and separation from ClientDlg are agreed and implemented.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- c
- Domain
- api, audio-video-rtc
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100