pimoroni / pimoroni/plasma-python
Add LED zones for multi-player support
Nobody has claimed this yet.
- Dominant language
- Python
- Stars
- 18
- Forks
- 9
- Avg merge
- 2d 57m
- Merged PRs (30d)
- 1
Description
This is a suggested alternative to #13 which has been conflicted beyond rescue.
- A zones section in plasma.conf where you can set a name with an offset + count
- hoist all the daemon's state out of
maininto per-zone state - add some way to specify zone in the pipe protocol
--zonein plasmactl
Instead of two daemons, it becomes plasmactl --zone player1 and plasmactl --zone player1 with the single daemon mapping all LEDs connected to the board, and the zone config deciding which player (or other feature, such as pulsing status LEDs, underlights, etc) controls which lights.
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by reviewing the current daemon state, pipe protocol, plasmactl entry point, and the existing configuration format, then compare the proposed approach with issue #13. Define how plasma.conf names zones, how offsets and counts map LEDs, and how zone selection reaches the daemon. Done means one daemon can control multiple configured zones through plasmactl --zone without the conflicted design from #13.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python
- Domain
- cli, embedded-iot
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Active
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100