The plugin API is not well defined, in fact plugin writers tend to use whatever they want (that’s Python), which will lead to issues since the Picard code they use may not be stable.
This is why there’s a plugin API version, but imho we need a complete rework and proper documentation. Help is welcome.
We plan to release 2.0 this autumn. After the end of GSoC a beta version will be announced.
A lot of code changed compared to 1.4, and prolly even more will in near future. Picard 2 is a port of Picard 1.4 to Python3/Qt5, and a lot of code can now be simplified. Another major change is the move to json web service instead of xml.
See above for release plans.
Plugins aren’t compatible, but most will be ported. The plugin archive (zip) format will change too (manifest file instead of hacky header variables, python 3/Qt5 etc…)
You need to enable
folksonomy_tags config option and then you should be able to access tags through
It depends, that’s done manually for now, usually i do it after important changes, feel free to ping me on IRC (
#metabrainz zas). It was done this morning (your plugin is available through plugin API now).
This should be improved in near future.