History and Philosophy

PlugBoard is born because of the need to create several plugin-based projects. These projects, currenly got a plugin management system many times different between each other and not much organized. So, we decided to create a shared plugin system to use in all kinds of environments (daemons, GTK, Wx, Twisted an so on).

Actually, we chose zope interfaces to gain a good abstraction level for both framework components and its based applications.

The framework tries to offer as much utilities as possible to create a plugin-based application and at the same time to be as much flexible as possible, so that the framework could be applied to all kinds of projects, as described before.

The framework phylosophy let the application base everything on plugins, then plugins will be the core of the application as well, even the programmer decide to let the core be pluggable.

Why PlugBoard?

PlugBoard is mostly be used for applications which need to be extensible trough a really flexible way. Eventough PlugBoard got several components for this purpose, you may not use them all or  use them by creating your own implementation.

PlugBoard could be apparently hard to understand and use, and it could appear too "big" for small projects, but making an appropriate implementation, it could be used as well everywhere.