> -----Ursprüngliche Nachricht----- > Von: Cor Bosman [mailto:[EMAIL PROTECTED] > Gesendet: Donnerstag, 7. August 2008 23:30 > An: Florian Lagg > Betreff: Re: [RCD] Plugin-Architecture > > > Currently I have plans implementing it this way (OVERVIEW): > > * There's a directory with plugins, e.g. ./plugins/* > > * Each plugin resides in a own directory, let's call it > "foo_plugin" > > for now. > > This assumes that there is a file called foo_plugin.inc > which includes > > a class foo_plugin > > * In the configuration, we have a simple array list of > enabled plugins > > $rcmail_config['plugins_enabled'] = array('foo_plugin', > 'bar_plugin'); > > * on the first called hook we initiate the rcube_plugins > class which > > is a singleton this class initalizes every plugin and - in the > > constructor of these - the plugins itself register to some hooks. > > this is done only once every request (because rcube_plugins is a > > singleton) > > * if registered hooks are called... ##### here's a small mistake: > > every plugin is called - one after another - in the order > given in the > > config above. ##### naturally we call only plugins registered to the specific hook - not all > > therefore an array of data is passed to each plugin - and at last - > > returned to the roundcube code. > > > > Have I missed someting? > > > > Look good! Thanks for doing this. > > Cor >
_______________________________________________ List info: http://lists.roundcube.net/dev/
