🚀 go-pugleaf

Well, this technique allows you to be more "free" from the toolkit and add
in your own twists, but I would only do it if you had good reason to. For
example, if you wanted to make some of your own "richer" versions of a
Button, then subclassing would be a good approach.

But if you only need default behavior, then don't waste your time, the
compiler's time, etc.

Remember, every line of code you write costs lots of money in maintenance,
etc. Using a library en toto is the more cost-effective means...

Here's a cool tool to view and create your classes (it's free and pure
Java):
    http://www.oi.com/togetherj.htm