Home
| pfodApps/pfodDevices
| WebStringTemplates
| Java/J2EE
| Unix
| Torches
| Superannuation
|
| About
Us
|
Java/J2EE Programming |
This package allows you find all the classes in your class path that implement a given interface. The standard Java library classes are not searched (unless you explicitly add one to your classpath) and only classes that have a no-arg public constructor and that implement the interface are returned.
The interface you specify can be any one that exists in the classpath. The classes found do not have to implement the interface directly but can do so via a superclass or via an interface the extends the the one you specifed.
WebStringTemplates is an easy to use Java template engine that separates web page design from the server coding.
Summary:
Present JSP/Servlet coding mixes HTML and Java/JSP. This makes it hard for the Web Designer to do his job and obscures the business logic for the Programmer. For the Systems Architect, this mixing of HTML and server code means there is no clear interface or separation between the server code and the web page design.
WebStringTemplates solves these problems with an easy to use package that has separate tutorial sections for the Web Designer, the System Architect and the Programmer. WebStringTemplates allows the System Architect to define a clean data interface between the the servlet/JSP and the web page. This Data Interface Definition file defines what data is available and provides sample data for development purposes. Once this interface is defined as a HTML document, the Web Page Designer and the Programmer can independently do their jobs without interfering with each other. It is the Programmer's responsiblity to ensure the data specified is available and correctly formatted, without having to worry about where it will be displayed on the page. It is the Web Page Designer's responsibility to display the data in a pleasing manner, with roll overs, drop down menus etc., but without having to worry about the actual data being displayed. The Web Designer does not even need access to a running server. More...
These Gui Utils are a grab bag of utilities for creating user friendly GUI Java Applications.
InputTipsManagerV1.3 (Updated 7th Jan 2006)
InputTipsManagerV1.3 lets you position input tips on JTable
cells.
This class lets you display a small message to the user when they enter an invalid input. It is usually used in conjunction with input validation. The include test screen illustrates a variety of application.
These Tips and Guidelines are primarily aimed at Graphical User Interfaces (GUI) applications but some of them are also applicable to general Java Programming.
Summary:
Most Java applications are trapped by the legacy of programmers brought up on Microsoft programs. Computers today have more power and storage than most people can use but users are still expected to struggle with programs that don't save their work, don't allow them to change their minds, don't recover from errors and give useless error messages.
These tips and guidelines for programming outline how to write
better GUI applications.
These tips cover:- error recovery, error
messages, logging, thinking like a user, dialog boxes, and what's
wrong undo/redo.
Summary:
How to stop a Thread is a perannual question
for Java programmers. Finally with the release of Java V5.0 (or
V1.5), which incorporates java.util.concurrent, a definitive answer
can be given. The answer is you stop a thread by using interrupt().
This article covers some of the background to stopping threads and
the suggested alternatives and discusses why interrupt() is the
answer. It also discusses interrupting blocking I/O and what else the
programmer needs to do to ensure their threads and tasks are
stoppable.
Adding Listeners to java.util.concurrent with FutureTalkerV1.3 (Updated 7th Jan. 2006).
Summary:
Java V5.0 (or V1.5 as it otherwise know)
incorporates Doug Lee's Concurrent package as java.util.concurrent
. This package provides many of the utilities needed for writing
multi-threaded programs in Java. One notable omission is a built-in
means to listen for the completion of a task. In Java V1.4, my
ThreadReturn
package provides this functionality and I have found it invaluable in
writing multi-tasking programs. This article
describes how to get the same functionality in Java 1.5 by building
on the hooks provided in the java.util.concurrent
package.
Here is a thread returns package to handle returns from threads in Java V1.4.
Summary:
Java has built in support of multi-threading,
but while it is easy to start a thread. It is difficult to stop one
and when a thread throws an exception, the exception disappears into
thin air. This article will describe how to use the
au.com.forward.threads
package to throw exceptions from
a thread back to the thread that is waiting for it to finish. The
package also allows you to return a result from a thread when it
finishes and to add ThreadListeners to your thread to be notified of
the results. Along the way you will meet WeakReferences and Java
V1.4's new exception chaining as well as being introduced to
Invariant Classes
The full package with documentation can be downloaded from here.
CreateLnk is a simple C program that will create a shortcut
on the Window's desktop.
With this short cut you can run you .jar
file directly from the desktop. You can also specify your own icon
for the link.
Contact Forward Computing and Control by
©Copyright 1996-2020 Forward Computing and Control Pty. Ltd.
ACN 003 669 994