• Want to receive the latest contracting news and advice straight to your inbox? Sign up to the ContractorUK newsletter here. Every sign up will also be entered into a draw to WIN £100 Amazon vouchers!

javax.swing package

Addanc

More time posting than coding
Joined
Sep 1, 2005
Messages
442
Likes received
22
Thanks received
3
Can anybody recommend any books that provide a coherent description of the usage of the GUI javax.swing package? Proper class diagrams etc.
 
I've downloaded the Sun docs, great description of components in isolation. My background is comms, kernels and drivers (no GUI). I'm looking for a good coherent overview of how these GUI components fit together.
 
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.
 
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 :freaky:

Excellent point about the UI thread :yay:
 
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 :freaky:

Excellent point about the UI thread :yay:

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.
 
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.

Ah right. I implemented TreeCellRenderer back around 1999, which is why my memory of the whole setup is a bit hazy :)
 

Advertisers

Back
Top