Plugin repository - totally user UN-friendly!
So I am a former mscore 1.3 guy who upgraded a while ago to 2.0, and I understand about moving from .js to .qhtml (xml?) format for 2.0 plugins, but what gets me annoyed is that there is nothing in the repository that lets you filter only plug-ins for 2.0.
While it looks like there are tons of plugins online, there are apparently few that will work for 2.0. I have to say being a cynic I suspect the reason that the repository doesn't offer a simple filter to sift out the .js files for those of us who have gone with the agenda and upgraded is that by keeping everything lumped together, it looks like there is more support for this platform than there actually is.
Comments
not .qhtml nor xml, but .qml. And indeed you are right, there is no simple way to turn .js into .qml, esp. if there is a GUI involved. There is, however, the ability to mark plugins for 1.x or 2.0, it is even mandatory. But this if very new, so most plugins are marked, and there currently is no method in place to filter, as far as I can see.
Thanks for raising the issue of the non user-friendly plugin repository. It's still on my to-do list. I'll see what I can do in the coming days. Keeping you posted.
In reply to Thanks for raising the issue by Thomas
@Thomas: some plugins work for 1.x and 2.0, but as of latest we have to chose which it is, same problem as with HowTos...
Can we have Checkboxes instead of Radio Buttons?
In reply to @Thomas: some plugins work by Jojo-Schmitz
For the how-to's, let's follow the strategy to migrate all of them to MuseScore 2. As long as it's not done, there will be flag in place to to warn that the how-to has not been updated yet for version 2.
For the plugins, Iim prepared indeed to put a checkboxes in place.