Thanks boroda74 for showing your interest in PM in developing a new plugin. Actually I have two ideas. Maybe one can be integrated into Additional Tagging Tools plugin, but it's your decision. Here are my ideas.
Template Manager
MB's problem with templates is the number of templates that can be used is limited and changing templates and storing unused templates are either quite cumbersome or not supported. This plugin will provide a way to store unused templates and effectively manage various templates used in MB.
1. Open the plugin under Tools menu or via a hotkey.
2. Select a section among three: virtual tags, external tools commands, custom web links.
3. Each section will show two tables (current and stored) with the same column sets.
<Virtual Tags>
Current
No. | Label | Formula | Descriptions
Stored
No. | Label | Formula | Descriptions
<External Tools Commands>
Current
No. | Label | Path | Parameters | Wait | Descriptions
Stored
No. | Label | Path | Parameters | Wait | Descriptions
<Custom Web Links>
Current
No. | Label | Web Link | Descriptions
Stored
No. | Label | Web Link | Descriptions
4. The user can move each line to anywhere he wants (either on the same table or to the other). Upon saving, the plugin updates both MB's settings file to reflect the changes made onto the current tables and the plugin's data file to save all.
Though the user could edit any cell on the plugin window tables, no need to support writing functions and fields like MB as it's assumed wrting formula is done on MB.
Backup and Restore Tool
It would be useful if a plugin can auto-save MB's xml database file regularly, and when something goes wrong it can assist the user in restoring lost tags. This would allow to import only specific tags from the xml file and thus give more choices to users migrating from other music players. Also it can work as a "tag time machine" since it stores all history of the tag changes made. Then users can keep tag history without having to store multiple versions of music files.
1. Open the plugin under Tools menu or via a hotkey.
2. On Backup section, the user sets how often it will save the xml file and how long it will keep each saved file. Also sets a path to backup. So this section displays the current settings and how many files have been stored since when.
3. On Restore section, the user could select one of the saved xml files to import. This will open a window where the user could select/deselect what tags to be imported. Upon applying it, the plugin will have MB rewrite database file via Library/Import command.
4. Each track shows a context menu command "Tag History". This will open a window where all tag changes made onto the track will display based on the saved xml files (probably the plugin needs to keep a master data file to handle this when each xml file is backed up). Then the user could select an old value to update the current tag value.
5. It could also support backup & restore of MB settings file.
