The AWT, Applets, and Swing School of （学校的applet,AWT和Swing）.pdf

The AWT, Applets, and Swing Mark Allen Weiss Copyright 1996, 1999, 2000 1 Outline of Topics The Abstract Window Toolkit – Basic ideas – User interfaces – Output items: canvases and graphics – Events – Fancy layouts Applets – HTML files – Converting an application to an applet – Restrictions 2 Basic Ideas The Abstract Window Toolkit (AWT) is a GUI toolkit designed to work across multiple platforms. Not nearly as fancy as MFC. Event-driven: the window is displayed, and when things happen, an event handler is called. Generally, the default event handler is to do nothing. Must import java.awt.* and java.awt.event.* 3 Evolution of GUIs Java 1.0 – basic AWT components – terrible event model Java 1.1 – same AWT components – new event model Java 1.2 – new fancy Swing components – same event model as 1.1 – not supported in all browsers, but plug-in available 4 To Swing or Not? If you are writing applications, Swing is by far the preferable option – faster – prettier – more flexible If you are writing applets, decision is harder – consumers not likely to have Java 1.2; can give it to them, but download will be time-consuming. Most consumers won’t bother and will go elsewhere – corporate clients can be forced to go to Java 1.2 5 AWT vs Swing Concepts are all the same. We