Java is enjoying a renaissance on the desktop. There are several reasons for
this The issues that plagued early client/server projects or Java desktop
applications have largely been solved. Swing 1.4.2 delivered great
performance improvements and good fidelity XP and GTK look and feel classes.
Java Web Start now exists as a way to deploy programs to a client PC that run
in a local JRE and enjoy the benefits of local caching, lazy update, and
execution within Java's security model
Java is becoming part of the default installation setup for many PCs vendors,
such as Dell, HP, Gateway and others.
SWT provides a set of rich native controls over and above those offered by
AWT, and many Java developers are finding this a useful GUI toolkit to use in
their end-user applications.
HTML is no longer being viewed as the only viable client for application
development. A numb... (more)
At the moment there seems to be an extremely unhealthy obsession in software
with the concept of architecture. A colleague of mine, a recent graduate,
told me he wished to become a software architect. He was drawn to the glamour
of being able to come up with grandiose ideas - sweeping generalized designs,
creating presentations to audiences of acronym addicts, writing esoteric
academic papers, speaking at conferences attended by headless engineers on
company expense accounts hungrily seeking out this year's grail, and creating
e-mails with huge cc lists from people whose signatur... (more)
A number of very significant development efforts are underway that bode well
for Desktop Java's future.
On the language side is the Java FX script project
www.sun.com/software/javafx/index.jsp. Java FX is neat because it provides a
high-level scripting interface that runs on top of the Java 2D API. From the
users' viewpoint it means they don't have to write Java code and, for better
or worse, understand the intricacies of threads, Java 2D or Swing class
hierarchies, timing frameworks, and so forth. Instead they just write script
that describes the desired GUI at a high level, in... (more)
The first part of this article (JDJ, Vol. 8, issue 4) introduced the Standard
Widget Toolkit (SWT), and showed how graphical user interfaces can be created
using some of the basic widgets found in SWT. In addition, layout classes
were described that allow widgets to be arbitrarily positioned and sized
within their parent.
In Part 2, we continue where the previous article left off, describing some
of the more advanced controls and concepts, including multithreading in the
user interface. We conclude with a brief discussion of SWT graphics.
Many of the advanced controls in SW... (more)
Recently I was having a discussion with a colleague about traditional versus
Web clients. Instead of hearing the usual defense about how much easier it is
to deploy and manage a thin client application, his point was that
client/server fails because fine-grained transactions don't work.
With a browser-based application, when collecting data the typical workflow
is the user inputting data on a number of pages and completing the
transaction with a final Submit button. The flow of navigation is tightly
controlled by the program that may create a session EJB to capture the data