OpenLightingProject / OpenLightingProject/open-fixture-library
Consider using the rdm.openlighting.org website as a source of data
Nobody has claimed this yet.
- Dominant language
- JSON
- Stars
- 258
- Forks
- 100
- Avg merge
- 11h 52m
- Merged PRs (30d)
- 53
Description
Hi Flo,
I commented similarly on another related endeavour, incidentally you guys should talk, it may also be another output format for you/input format for afterglow ( https://github.com/brunchboy/afterglow/issues/1 ).
Anyway, we already provide some basic personality info that we capture for fixtures, see for example:
http://rdm.openlighting.org/model/display?manufacturer=21075&model=84
But we actually capture a lot more in the background (although I'll admit I'm not certain if it's currently thrown away, or is actually stored in the back end and just not presented), e.g.:
https://github.com/OpenLightingProject/ola/files/1107996/robin_dl7s_profile.robe.txt
Essentially you could make use of this info (via some API), to pre-populate/produce initial templates for your fixture library. so users don't have to do some of the basic typing.
Contributor guide
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
No implementation files or tests are named. Start by reviewing the RDM Open Lighting website example, the linked fixture profile, and related Afterglow issue #1; determine whether the captured data is available through an API and define the scope for generating initial fixture-library templates.
Written by the indexing model from the issue text.
Assessment
- Domain
- backend, data
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 20/100