Determine how the Beat and Bassline Editor should work
Nobody has claimed this yet.
- Dominant language
- C++
- Stars
- 10.4k
- Forks
- 1.3k
- Avg merge
- 2d 13h
- Merged PRs (30d)
- 7
Description
I'm opening this issue on the main tracker instead of [here](https://github.com/HDDigitizerMusic/lmms-alt-theme/issues/1) because from what people have been saying, it seems like the current BB editor is not ideal, and it's more from a technical standpoint than just aesthetic. Hopefully, the conversation can be opened up to the LMMS team instead of just the people who were on the [`Modern Noir` fork.](https://github.com/HDDigitizerMusic/lmms-alt-theme)
What would the Beat and Bassline editor ideally look/work like? Maybe after we have that established, we can then come up with a solution based on those standards.
> We're still trying to determine what it should work like... I think ideally, the patterns would all grow and shrink together. Then perhaps a way to prevent squishing the steps smaller than their natural size. ~ @tresf
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 existing Beat and Bassline editor and the linked Modern Noir issue, then read the discussion on the main tracker. Define the desired editor behavior, including coordinated pattern resizing and minimum step sizing; the work is complete when the team agrees on clear standards that can guide a later implementation.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- cpp
- Domain
- desktop
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 20/100