> On 11/29/06, Johan Compagner <[EMAIL PROTECTED]> wrote:
>> what makes a formcomponent a formcomponent?
>
> That, of course, is the main question :) But not an easy one,
> certainly not to extract a robust interface from it. The component
> like I proposed (but that should have the header stuff included) works
> fine though, so this might be a better solution than forcing ourselves
> into interfaces when we're still unsure about what the best are.
>
> Eelco
>
May would be interesting to try it from the other end - what makes Panel a
panel ? A lot of components (not only form) can have except its own
behaviour the behaviour of panel ...
saki
