> > Plugin or not... always debatable, I guess. > > > > Take LDAP addressbook support, for example - isn't that something that > > could > > also be provided by a plugin? It also requires configuring a backend system > > (an LDAP directory). > Absolutely - if there is a flexible framework almost everything except > the framework itself can be a plugin - with some plugins required (see > Typo3 for a great sample of this!). > But unless this Plugin system is done its hard to implement something > like this without patching the sources.... so first job: plugin > architecture!
Jeroen, could you provide me a patch for your plugin? You may have read that I want to implement a plugin architecture here - it would be great for me to see how you implemented this. Your "plugin" is configureable on the web-view of RC, so it is a plugin involved in the backend and frontend. Depending on this I can find out (hopefully) where you need hooks to implement this plugin without patching if you use my plugin architecture. We had some questions about this here on the list but inspecting code is always easier. It couldn't be a solution to carry 3rd party products as diff patches to specific versions - this way you could never implement 2-3 plugins with ease. Pls. send your patch to the list. Thanks. _______________________________________________ List info: http://lists.roundcube.net/dev/
