What is a good guideline for interface usage ? There was a time where i literally created one interface for each of my components... and currently i try to avoid them in component based environments... So either i overuse them, which generates messy code... or i dont use them at all :p

from a regular developer pov: use interfaces where you expect to have multiple implementations. Interfaces define a contract that must be adhered to

E.g. my components have an interface that defines methods to check if they're dirty

and another that forces them to implement a method to clone the component

Thanks ! Well i often code my components in a... extendable way using callbacks, events and other techniques ( Was that called SRP ? )... so i dont see that many options to implement those.

Thats a technique i have never heard of :D

Sounds like Utility methods ^^ Or extensions

Hmm... i took a quick look at them, they look completly different :o but kinda interessting

Correct me if I'm wrong, but another name for it would be 'Method Overloading'