[Feedback Needed] Split plugins into categories #713
Labels
No labels
awaiting-reply
breaking changes
bug
cannot-reproduce
dependencies
documentation
duplicate
electron-issue
enhancement
fix-available
good first issue
help wanted
invalid
javascript
need more information
need rebase
official-youtube-music-issue
plugin request
question
release
security
stale
Status: blocked
typo
wontfix
ytmd-issue
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference: YTMD/youtube-music#713
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
There are currently 25 plugins, which are all listed in alphabetic order in the menu
I think its a bit much, it's hard to read, and also if using the
in-app-menu
plugin, the list depends on window size (if there isn't enough space, it cuts some of the plugins)I propose splitting the plugins into categories, which will only affect the menu - each category in its own submenu
Categories could maybe be like:
Would love to hear thoughts from anyone
about the whole idea, and also specifically the name of the categories and the way they are split
I generally like the idea. For Sponsorblock, I'd say to put it in both Playback and Integration if that's possible. For the last category, I'd recommend naming it Other since they really have not that much in common and we'll need this category anyway.
I think that this is definitely a good improvement.

I made a mock-up of what I think would be a better solution: Opening an options window when the plugins menu is clicked. I'm not sure how easy/possible this would be to do, but it would be a lot nicer than a bunch of menu/submenu items.
Either way, I agree something needs to be done. The plugins list is almost taller than my monitor (it actually scrolls a few pixels).
TODO since it seems no one has the time to write a full settings menu implementation, maybe use something simpler like
https://github.com/snapcrunch/electron-preferences
could take some design inspiration from https://web.dev/building-a-settings-component
+1 for this
We working on this