Plugins Vs Extensions etc. #35464
Replies: 1 comment
|
The docs really are scattered right now, so you're not missing something obvious. There's an open issue about exactly this: #34210. Here's how it looks in 4.6, based on the source. There's one system now, and it loads two formats. Since 4.4 the "extensions" framework is what runs everything in the Plugins menu. In 4.6 it loads both kinds side by side (extensionsprovider.cpp):
Either way, they show up in Home → Plugins, where you enable them, and then appear under the Plugins menu. Which API you get depends on
Interesting detail: MuseScore itself ported a couple of its bundled plugins to extensions in 4.6, and they use What I'd do as a web dev starting today: write against the old (v1) score API, because that's the one that's documented and that real plugins use. Pick your packaging:
Docs to keep open:
I'd treat the v2 API as something to move to once it's documented, not something to start on right now. Disclosure: this answer was drafted with help from an AI assistant (Claude). I checked it against the linked v4.6.5 source and docs. |
Uh oh!
There was an error while loading. Please reload this page.
I am using MuseScore 4.6.
I want to create a plugin, (I am a web developer)
I cannot figure out what the state of the plugin/extension system is from the available information. Should I use the V3 plugin system and port it to V4, as the V4 extension system isn't working or isn't documented, or is the V4 developed and documented somewhere I'm not seeing and I should use that?
Any help would be appreciated, I want to start off on the right foot. Thanks.
All reactions