Hi, > 5. 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. I think auto-loading a plugin because of its presence is a bad idea. There should be a global conf that turns them on or off. This would solve point 5 as well, as the order in the conf decides their priority. > $rcmail_config['disabled_plugins'] = 'plugin2 plugin3::mail-compose.* > plugin3::settings.*'; I would do it the other way around. All plugins are disabled until you enable them in the config. Just to make sure. The plugin system we're talking about here doesnt just allow actions, but also small hooks everywhere throughout the code/templates? The way to create a vast array of useful plugins is to create hooks everywhere. Cor _______________________________________________ List info: http://lists.roundcube.net/dev/
