Re: Overriding JComponent or implementing ComponentUI?

Lew allegedly wrote:
> Daniele Futtorovic wrote:
>> FWIW (as it's been a while I've done GUI code), the more complex and
>> specialised custom components I wrote, the further I lent towards
>> ComponentUIs. Unfortunately, I don't remember any exact benefit. Perhaps
>> a matter of cleanness and encapsulation (as it feels "more right" to put
>> that code in a dedicated place, rather than overriding stuff in the
>> component). There's also the issue of shared resources, although those
>> can be dealt with similarly in JComponent.
>>
>> I realise that was a terribly useless post. Sorry about that. :)
>
> Honestly, I thought it was going to be useless for a second, but it
> turned out to be rather thought-provoking and best-practice oriented.
>
> Assuming I understood your remarks correctly.
>
> Josh Bloch says, "Prefer composition to inheritance."
>
> In GUI terms this translates to, "Usually you have a JFrame as a member
> rather than as a supertype."
>

Indeed the good man does, and indeed the good man is right. But I would
have liked to be able to find in my experience a pratical illustration
of that bit of wisdom. For, while trust may be fine, knowledge is good. :}