mirror of
https://github.com/mumble-voip/mumble.git
synced 2026-03-03 00:46:56 -05:00
Plugins: Add config dialog for plugins #2970
Labels
No labels
GlobalShortcuts
Hacktoberfest
accessibility
acl
asio
audio
bonjour
bsd
bug
build
certificate
ci
client
code
documentation
external-bug
feature-request
gRPC
github
good first issue
help wanted
help-needed
ice
installer
linux
macOS
needs-ckeck-with-latest-version
needs-more-input
overlay
positional audio
priority/P0 - Blocker
priority/P1 - Critical
priority/P2 - Important
priority/P3 - Somewhat important
priority/P4 - Low
public-server-registration
qt
recording
release-management
server
stale-no-response
stale-support
support
task
test
theme
translation
triage
ui
windows
wontfix
x64
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference
starred/mumble-mumble-voip#2970
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?
Originally created by @hbeni on GitHub (Mar 19, 2025).
Context
Plugins / Configuration of plugins trough standard means and mumble client.
Description
It would be cool to have some built in config mechanism for plugins:
Currently I use ini files to let the user setup their preferences, which is technically not so easy for most users.
Mumble component
Client
OS-specific?
No
Additional information
@Krzmbrzl commented on GitHub (Mar 19, 2025):
Yeah, this has been on my wish list pretty much ever since I worked on the plugin framework :D
Unfortunately, this will require quite some work, which is why I haven't gotten around to it yet...
@hbeni commented on GitHub (Mar 19, 2025):
In Case this gets added - can it be done in a way, that new plugin versions supporting configurability are still compatible with pre-plugin-configureable mumble versions?
@Krzmbrzl commented on GitHub (Mar 20, 2025):
Yeah, I would imagine this to work similar to other parts of the plugin API. That is, it gets used if Mumble knows about it and the plugin provides the necessary callbacks. Otherwise, the functionality just won't be there.
@hbeni commented on GitHub (Mar 20, 2025):
Ok, just so I understand:
I can compile a plugin against plugin-api Version n; and a mumble client that just knows about n-1 can load and use that plugin?
@Krzmbrzl commented on GitHub (Mar 20, 2025):
Yes. See for example
github.com/mumble-voip/mumble@d114c08add/src/mumble/Plugin.cpp (L183-L188)for how this is handled.