Florian Lagg wrote:
I hope I could provide a small patch on monday for testing.
I made it. The Patch is made with SVN Version 1626. I implemented it slightly different. I'll describe it here:
For me it looks good, but we need few "must have" features at start:
- Auto-calling plugin actions for build-in tasks/actions, it means we
should add (in index.php) code for automatic calling of actions e.g. 'mail-compose-before', 'mail-compose-after', 'mail-sendmail-before', etc. and probably also 'mail-before', 'mail-after', etc. 2. Possibility to use own tasks/actions (I mean /?_task=settings&_action=myaction or /?_task=mytask) 3. Javascript part - for javascript functions/actions (in similar fasion) including point above. 4. Possibility to add UI part from plugin without skins modification. It's "must have", but I think, we can live without that for now.
And not exactly "must have", but my "would be nice" ideas for future:
- Actions priority - if we have few plugins for the same action which
should be executed first? 6. Config option(s) for enabling/disabling plugin parts. Let's say we have a plugin with few features, but we need only one. Ok, we can have separate configuration for each plugin, but maybe something global? Let's say using regexp. It may be used for temporary disabling whole plugins without removing files from plugins/ dir. E.g.
$rcmail_config['disabled_plugins'] = 'plugin2 plugin3::mail-compose.* plugin3::settings.*';