Standardize Plugins Layouts
Open
Nobody has claimed this yet.
conversation
enhancement
gui
meta
- Dominant language
- C++
- Stars
- 10.4k
- Forks
- 1.3k
- Avg merge
- 2d 13h
- Merged PRs (30d)
- 7
Description
Enhancement Summary
Currently, our Lv2 and LADSPA designs differ a lot (feel free to fix/update this table):
| CLAP | LADSPA | Lv2 | VST | VST3 | Suggestion | |
|---|---|---|---|---|---|---|
| Linkable Models? | No | Yes | No (surprising) | ? | No | No (#7201) |
| HiDPI redesigned controls | No | Yes | No | ? | No | Yes (#6798) |
| Checkbox for booleans | Yes | No | Yes | No | Yes | Yes? |
| Spinbox for integers | Yes | No | Yes | No | Yes | Yes? |
| Code base for Layout | ControlLayout | "LADSPA" | ControlLayout | "VST" | ControlLayout | Common? |
Relevant PRs/Issues:
- #6456
- #6798
- #2068
- #7201
Involved Developers:
- @michaelgregorius (HiDPI redesigned controls)
- @DomClark (VST3, #6456)
- @zonkmachine (#6798)
- @JohannesLorenz (Lv2)
- @messmerd (CLAP)
Implementation Details / Mockup
The implementation depends on whether we want to spend time making LADSPA, Lv2 and VST and VST3 share the same Layout.
- If yes, we would only need to fix it in one layout, e.g. ControlLayout
- If not, there will be a lot of different subtasks (like "Let Lv2 use HiDPI controls", "remove linkable models from LADSPA" etc)
Please search the issue tracker for existing feature requests before submitting your own.
- I have searched all existing issues and confirmed that this is not a duplicate.
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 issues #6456, #6798, #2068, and #7201, then compare the CLAP, LADSPA, Lv2, VST, and VST3 layout behavior described in the table. The issue does not name files or tests; done requires deciding whether layouts should be shared and defining the resulting plugin-specific subtasks.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- cpp
- Domain
- design, desktop
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 20/100