Plugin Architecture: Hooks and Callbacks

[eluser]Grahack[/eluser]
When I saw your extensivity thing, I first thought about a simple Vanilla-like delegation.
My idea is quite simple, but maybe too simple for you.

Using a very early hook, we discover plugins in a special (and of course configurable) directory. Those plugins are simple callbacks declarations and registrations, that we 'include'.

Code:

// in the plugins files: the injected code
function my_function()
{
$var &= $ci->plugin_lib->param('param_id');
// some processing
}
$ci->plugin_lib->register('my_function', 'moment_id');

Code:

// anywhere else: where we want to inject some code
$ci->plugin_lib->add_param('param_id', $the_param);
$ci->plugin_lib->moment('moment_id');

The 'moment' function then calls every function that has registered to act at the 'moment_id' moment.

About the name, CI has (had) already a 'plugin' thing. Vanilla calls this 'delegation', if I were the boss, I'd call this 'injections'.