🚀 go-pugleaf

Jason Cwik wrote:

> I've gotten it to work. You just need to make sure you are using the newest
> version of SWING. 1.0 DIDNT work with applets, but 1.0.1 and later will.
>
> In my latest applet, I've been using the Java plugin and that works quite
> well in both browsers...
>

Thanks, Jason. I think a lot of people missed my point because of the subject
string.

I already know Swing applets will work if they're signed and we use the Java
plug-in. The whole point of my posting was that with the release of Swing,
JavaSoft has moved us to a new era. Now you have to SIGN ALL APPLETS TO MATTER
WHAT. Remember, before, we only had to sign applets if they attempted to leave
the sandbox. That's no longer true! Now, anytime you write an applet, if you use
Swing to do the interface, you have to sign it - period.

To me, this is a hassle. It means I'm not going to use Swing for my applets: I'm
going to get some GUI toolkit of lightweight components so I don't have to roll
my own. My applets don't write or read files on the client machine or connect to
some random host, and applet security is a screaming nightmare if you want to
support both browsers (which I do.) I should not have to sign my applets, or use
the Java plug-in; my customers have browsers that can run 1.1 code.

It just seems a little unforthcoming on the part of JavaSoft to make such a
significant change without clearly stating they were doing so, especially when
you consider that they were earlier touting Swing as a replacement for the AWT
and asserted quite loudly that there is now no need whatsoever to use the older
components.

Cheers,

Ken