The typo3 approch is a bit heavy. But plugin registration with "event" and "action" is a good idea. The core trigger an event, and every plugins wich listen this action can do something. The classical trouble, is how describe event? xml, annotation like syntax? Wich order action is done? Wich context can read an write the plugin? Dependance and conflict of plugin? The first step is to forbidden "echo" in plugin action.

I've got some example of such code.

M.

Hans-Christian Otto a écrit :

Well, yeah, a plugin architecture would be great, but there are a couple of problems, one would have to think about while implementing this. What should a plugin be able to do? How should a plugin be able to extend the default rc code? The CMS typo3 uses a kinda sensefull plugin architecture, maybe one should have a look on it - thinks like extending the codebase with hooks sound pretty usefull for me. Regards, Christian -- Hans-Christian Otto www: http://muh-die-kuh.de mail: c.otto@lab9.de jabber: muh-die-kuh@jabber.ccc.de icq: 127751895 gpg: 0xE5004DA3