Feb 23, 2012 06:21 PM|Horizon_Net|LINK
it depends on your requirements. If you want to have a generic control it could become complex, but it will fit into more scenarios. If you want to have a control which is only created for one purpose (in a sense of reusability) you should keep it simple
(it only should do for what it is created and the rest should be handled anywhere else).
For the simple scenario: You can create a base control from which other controls (depending on their purpose) can inherit and add additionally complexety. That should be the best way if you follow an OOP design, reusability, and understanding.