🚀 go-pugleaf

First, if you are developing applets for the Internet (not a company
intranet), the usual advice you find in the newsgroups is to use JDK
1.0.2 and not use swing.

If you *really* want to use JDK 1.1.6 with swing (as JBuilder insists on
doing in most cases) and deploy to the internet, then do the following:

Go to Sun's Java site and get the file that converts HTML files so that
Sun's Java plugin is used.  This gives the browser swing capabilities
(and JDK 1.1 if an older browser is used).  Also get and install the
plugin on your PC.

Of course, JBuilder's jar files include swing and (I think) 1.1 stuff,
which isn't needed if the plugin is used (and makes a jar download much
longer over a modem).  Consider avoiding including these in the jar (or
not use jar).

Using your edited HTML files using Sun's converter, when a client
accesses your web page, the plugin is checked and if not found, the user
is sent to Sun's site to download it.  This happens once, since once
installed, the user's plugin will kick in every time your page is
accessed.  This saves a lot of time opening the Java applet (not having
to download swing, and 1.1).

The down side to all this is that Mac users are left in the cold.

BTW, I seem to recall reading here that JBuilder is really best used to
generate applications, not applets (unless they are to be used in an
intranet environment).  For the internet, though, using JDK 1.1 and
swing leads to many problems!
-- 
Pierre A. von Kaenel
Math & Computer Science Dept.
Skidmore College
Saratoga Springs, NY 12866