> True, it's been weighing the disadvantages vs the advantages, and so > far, ensuring that we wouldn't paint ourselves in the corner too > quickly won over flexibility.
To make this 'painless' though, we'd probably need a whole bunch of interfaces. We've looked into moving to a more interface based approach in the past for Wicket, but we concluded that it just got too crazy, increasing the complexity of the API considerably, and had all the disadvantages of interfaces over abstract classes (no guaranteed behavior, everything has to be public and abstract). We might just come to that same conclusion again. --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
