Eric wrote:
I was just wondering if there is a strategy going forward on how plugins should be written and how they should be implemented. The instructions for piwik seam to be odd to include a require_once in config.php to load the plugin.
Yep, that's about it. Plugins should inherit from Plugin, should call parent::__construct() in their constructor, and should implement methods like onEventName($arg1, $arg2) for each event they want to handle.
On the same note how will we make different authentication a plugin? (basic/ldap/openid/etc)
We're going to use PEAR's Auth system for authentication plugins. It's already written, it's fairly complete and well-maintained, and it's got a lot of existing drivers.
It is something i'm interested in and would like to devote some time to, but dont want to duplicate effort. If no one has put much time into this yet I have some ideas we can discuss and hopefully find a good solution.
Code has not yet been cut, and if you have other ideas or ways of building this, I think we should get it going. It's an 0.8.x dev priority, so I'd like to see it get started soon.
-Evan _______________________________________________ Laconica-dev mailing list [email protected] http://mail.laconi.ca/mailman/listinfo/laconica-dev
