Plugin development guide

[mrhenko]

We need a document that stipulates what kind of functionality a plugin needs to have.

I suggest a simple text document (Markdown formatted) inside the plugin folder.

[larsemil]

I say we rather use the wiki on github for documentation purpose. Easy to read, easy to maintain.

Will leave open as this still is needed, allthough rather closer to sharp release then beta.

Also: we need to force the behaviour rather strict by implementing a interface for the plugins, this i will take care of!

[mrhenko]

I completely agree regarding the wiki. Good idea!

However I disagree about it being a feature in the sharp release. I think the best way to maintain a consistent API, especially now that we don't all sit in the same room and code, is to thoroughly document it both in the wiki and in the code.

[larsemil]

okidoki

[larsemil]

I have rewritten the plugin section a tiny tiny tiny bit and exchanged the parent function with an interface that forces new plugins to have the correct set of functions.