🚀 go-pugleaf

I personally steer clear of JBCL and dbSwing, and use plain Swing and JDBC.
Our applets are only deployed on an Intranet.

I assume that you are prepared to insist that users download Javasoft's Java
Plug-in? If so you won't need the javax.* packages in your JAR. If you use
only a part of JBCL/dbSwing then running dash-o Pro on your JAR may save you
a lot of space. It will reduce your JAR size by > 10% (perhaps much more)
anyway.

If you don't insist on plug-in use you'll need to include Swing in your JAR.

The painful feature of the plugin is that I can't see how to get it to cache
JARs on disk. Does anyone know how to do this?


WRBacon wrote in message <7ac1n8$6v912@forums.borland.com>...
>Hello again,
>
>I am having a problem with a large jar file, it's almost a megabyte in size
>and my applet must be deployed on the Internet.!  The applet must contain
>live data, therefore we want to use JBCL or dbSwing components for RAD
>development (we are currently using JBCL).   Question:
>
>*  If we require our clients to download and install a plug-in,  will this
>significantly reduce client download time of our applets?  If so, which
>data-aware components should we use, dbswing or JBCL?  What plug-in do we
>need and where is it?

Its at www.javasoft.com, and you need either the 1.1.x or 1.2 plugins
depending on which JRE you are targetting.

>
>Thanks a million,
>Redding Bacon
>reddingbacon@hotmail.com


Tom