Apple WebObjects 5 - Manual (Page 75)

C H A P T E R 6
WebObjects Desktop Applications
Two Approaches to Java Client 75

Apple Computer, Inc. January 2002
techniques work at a higher level than raw Swing. You’ll also save time by learning
the Direct to Java Client customization techniques rather than rolling your own Java
Client interfaces in Interface Builder or in raw Swing.
Although it is possible to build and use completely custom Java Client applications
(thus not using the
eogeneration package or XML user interface generation), there
is little benefit in doing so. Using custom interfaces ( .nib files) in Direct to Java
Client applications is the most sensible way to integrate completely custom
interfaces in your Java Client applications.
Table 6-1 Comparison of Java Client and Direct to Java Client
Task Java Client Direct to Java Client
Customization
options Interface Builder and raw
Swing. Assistant, XML freezing,
Interface Builder files, custom
controller classes, controller
factory delegates.
Development
time Rapid. User interfaces are
automatically generated but
are also easily customizable. Moderate to heavy depending
on user interface design.
User interface
synchronization
with data model Difficult. User interface not
synchronized with data
model once user interface
building begins. Synchronization happens
throughout much of the
customization process.
Localization Must use different interface
files. More automatic using
localizable strings tables.