Applet lifecycle quirks

Newbie & Debugging Questions
#1

Can someone point me towards any info on the various quirks of the applet lifecycle in different browsers etc.? I know that techincallly it should be a nice simple init() -> start() -> update() -> stop() -> destroy(), but I know that different VMs / browsers have a whole heap of quirks that can cause deployment issues.

At the moment I’m also using JApplet, which I’ve seen mention of causing problems as well instead of straight Applet. Is there a cannonical ‘best’ way of implementing an applet for maximum compatibility (bearning in mind that I don’t want to use a framework like pulpcore).

Ta.

#2

I know this is offtopic, but you might want to prefer deploying your application with an installer.

Now you’re at the mercy of infinite permutations of JRE+plugin+OS bugs / Oracle crippling the plugin even further / browser vendors being lazy, and I can tell you: it sucks.

#3

( first, you can control the applet life cycle using the Applet booter I ve posted on the shared section from java 1.1 to lastest release 1.6 )

anyway here are some info that may help :
init called once when applet is loaded
start called every time applet is activated/resume : web page changed / minimised (not working the same every where )
stop called every time applet is deactivated/paused (not working the same every where )
destroy called once when applet is unloaded

a cupple of setSize(…) & paint are called too (not working the same every where)

#4

Yes, I was looking at that but wasn’t quite sure exactly what it’s supposed to be offering. Do you have a proper project page / downloads for it somewhere?