Okay, so here's the list I sent Kristine in an email a few minutes ago. I figured I'd make it public just to see if anybody else had any ideas or comments.
Plugin Manager Requirements (i.e. tasks it should perform for the user)
- Lists
- Get list of plugins from official site
- List all plugins
- List installed plugins
- List non-installed plugins
- Individual Plugins
- Check plugin requirements (Perl modules and MT version)
- Install a plugin
- Upgrade a plugin (when a new version is released)
- Uninstall a plugin
- Provide links to plugin information
- View installed plugin documentation
- Configure plugin (see: my interface plugins idea)
Any thoughts?
; "Feed Stats Widget")
; "Google Referrer")
; "MediaConsumer Template Output")
; "MediaConsumer List Items")
; "MediaConsumer Edit Item")
; "mt-qotd.png")
; "Vox-qotd.png")
if it's going to detect requirement, i think i should add that, some plugins require "postproc.pm" whiles some dont depending on which version of MT they're runing on.
You'll have to find a way of letting the plugin manager know when to install it and when no to.
You probably have thought of this already though.
That's basically a version dependence, as far as I can tell. 2.5 has it, 2.21 doesn't. And one of the first things I put into the XML spec was the MT version requirement. :)
I'll be sure to mention that in the official Requirements list though. Thanks for pointing out the omission.