Java201.com

• Make Your Swing App Go Native, Part 1 by Joshua Marinacci   - [Clicks: 13]
  This is the first of a three part article series in which we will build a simple application from the ground up and make it look and feel native. This article will cover designing the menus and adding visual alerts. … Throughout the series, we will make use of several libraries and techniques that automate the process and make building high-quality Swing applications as easy as possible.
  http://today.java.net/pub/a/today/2003/12/08/swing.html - Dec, 2003
• Swing, Threads, and Events by Marcus Zarra   - [Clicks: 29]
  I normally spend a few hours every week reading the discussion forums at the Java Developer Network (http://forums.java.sun.com) and find that one of the most common problems is Swing and how it works in a multithreaded environment.
  http://www.sys-con.com/story/?storyid=38108&DE=1 - Dec, 2003
• Create client-side user interfaces in HTML, Part 2 by Allen Holub   - [Clicks: 27]
  This "Create Client-Side User Interfaces in HTML" series continues by examining the HTMLPane sources. Part 2 offers examples of how to customize the JEditorPane to support custom tags and also provides an extended description of the Factory Method design pattern.
  http://www.javaworld.com/javaworld/jw-11-2003/jw-1114-toolbox.html - Nov, 2003
• Create client-side user interfaces in HTML, Part 1 by Allen Holub   - [Clicks: 31]
  This article presents a variant on Swing's JEditorPane that makes it possible to specify an entire screen of your client-side user interface (UI) in HTML. JEditorPane is designed to let you put an HTML text component inside a dialog box, not to specify the entire contents of the dialog box in HTML. In practice, this class makes it vastly easier to create complex user interfaces than does Swing/Abstract Window Toolkit (AWT)'s standard containment-and-layout-manager architecture.
  http://www.javaworld.com/javaworld/jw-10-2003/jw-1003-toolbox.html - Oct, 2003
• Customize SwingWorker to improve Swing GUIs by Yexin Chen   - [Clicks: 28]
  The presentation layer of Swing-based applications mainly consists of event-handling logic, layout properties, and graphical user interface (GUI) components. While such code should be easy to program because of the Swing programming model's single-threaded nature, more complicated concurrent constructs such as SwingWorker are often needed to perform time-consuming tasks while preserving screen liveliness. In this article, Yexin Chen discusses some negative consequences caused by SwingWorker usage and illustrates how to customize SwingWorker to achieve additional architectural design goals.
  [Includes source code]
  http://www.javaworld.com/javaworld/jw-06-2003/jw-0606-swingworker.html - Jun, 2003
• Java Tip 137: Manage distributed JTables by Jeremy Dickson   - [Clicks: 33]
  When displaying tables with tens of thousands of rows (or more), it is imperative they quickly respond and display. One way to achieve this is by using a specialized TableModel that retrieves data from a server only when it is required, thereby minimizing data download. To further improve efficiency, row data can be retrieved in chunks of 50 rows and cached on the client side for future use. This article explains how to write such a distributed table and presents some of its advantages.
  [Includes source code]
  http://www.javaworld.com/javaworld/javatips/jw-javatip137.html - Apr, 2003

[Top]

• Multithreading in Swing by John Zukowski   - [Clicks: 22]
  In nearly every tutorial on the Swing component set, the component set has been described as single threaded, that is, all accesses to a realized component must be done from the event dispatch thread. The term "realized" essentially means displayed on the screen. In practice, this means that prior to showing a Swing component on the screen, you can build up a screen and get and set the necessary properties.
  http://java.sun.com/developer/JDCTechTips/2003/tt1208.html#1 - Dec, 2003

[Top]