Difference between revisions of "Development/Season of Docs/2019/MusicBrainz Picard"

From MusicBrainz Wiki
(Created page with "==Ideas==")
 
(Added suggestion for expanded plugin developer information.)
Line 1: Line 1:
 
==Ideas==
 
==Ideas==
 +
* Expand the existing documentation for plugin developers to clarify the required elements (e.g.: standard license types / abbreviations to be used), and the information provided in the arguments to the various plugin types (e.g.: structure of the JSON / Dictionary for '''''AlbumMetadata''''', '''''TrackMetadata''''', etc.).  Also include information about limitations (e.g.: what Python modules are built into the Picard release and available for use).  Include information regarding how to include and hook settings page(s) for the plugin into the Picard option settings tree, and how the settings page is developed (e.g.: using Qt) and compiled (e.g.: using the Picard <code>setup.py</code> script's <code>build-ui</code> command).

Revision as of 18:10, 17 April 2019

Ideas

  • Expand the existing documentation for plugin developers to clarify the required elements (e.g.: standard license types / abbreviations to be used), and the information provided in the arguments to the various plugin types (e.g.: structure of the JSON / Dictionary for AlbumMetadata, TrackMetadata, etc.). Also include information about limitations (e.g.: what Python modules are built into the Picard release and available for use). Include information regarding how to include and hook settings page(s) for the plugin into the Picard option settings tree, and how the settings page is developed (e.g.: using Qt) and compiled (e.g.: using the Picard setup.py script's build-ui command).