posted 18 years ago
Heavyweight components create UI components in the native UI. So an AWT button is a Windows button. Lightweight components draw UI components. So a Swing button is a picture of a button. Now, where can Swing draw a component? On a heavy one. But Swing can draw a bunch of lightweight components on one heavyweight canvas so it has far fewer heavyweight components at runtime.
The original theory was that the AWT approach would be faster as drawing is done by API calls to the OS. But it led to OS dependencies and the "weight" problem. So Swing was added as an alternative.
UI experts check me ... is that right so far?
A good question is never answered. It is not a bolt to be tightened into place but a seed to be planted and to bear more seed toward the hope of greening the landscape of the idea. John Ciardi