http://java.sun.com/docs/books/tutorial/uiswing/
As for how they fit together, basically all components extend the base component and implement a couple of methods to paint themselves and fire events. This all happens on one thread (the event despatch thread), so you should never, ever run any code of your own on the current thread or you'll lock the GUI - always run your own code inside it's own thread(s). This is the most basic mistake that most beginners make and also why there are so many crap Swing GUIs out there leading people to believe that Swing is slow.


Correct me if I'm wrong, but don't Swing components delegate their painting to a Renderer object, rather than a paint method? This decoupling is what allows for pluggable UI rendering... although it's been a while since I did any Java UI stuff, so maybe I'm remembering it incorrectly
Excellent point about the UI thread![]()
public void paintComponent(Graphics g) {}
is the method you override if you want to change how a component displays.
There is a Renderer interface which allows you to change what you do with the components (i.e. you could have a PrintRenderer that dumps straight to a printer) though it's very low level and personally I've never seen it implemented.
