blindfish wrote on Jun 3^rd, 2010, 3:37am:

For the record, this is safe (just allocating some memory), it is populating a PImage with a loadImage() outside of setup() which is unsafe.

Otherwise I am lost, the security warnings are strange...
Re-checking... (gosh, this uploaded.to site is slooow! and I hate it spawns a new full Firefox window!)
No, I see no potential security breach, like trying to save high score or such.

Hmmm, I made these changes, but the html-version still doesn't work with me.
Could you upload your version to uploaded.to? Pleeease....

Ok:

The music starts, and the background color is set. But the applet comes in a small window (I guess, 100 x 100 pixel).

And here is what the console says:

security: property package.access value sun.,com.sun.xml.internal.ws.,com.sun.xml.internal.bind.
security: property package.access new value sun.,com.sun.xml.internal.ws.,com.sun.xml.internal.bind.,com.sun.javaws
security: property package.access value sun.,com.sun.xml.internal.ws.,com.sun.xml.internal.bind.,com.sun.javaws
security: property package.access new value sun.,com.sun.xml.internal.ws.,com.sun.xml.internal.bind.,com.sun.javaws,com.sun.
deploy
security: property package.access value sun.,com.sun.xml.internal.ws.,com.sun.xml.internal.bind.,com.sun.javaws,com.sun.
deploy
security: property package.access new value sun.,com.sun.xml.internal.ws.,com.sun.xml.internal.bind.,com.sun.javaws,com.sun.
deploy,com.sun.jnlp
security: property package.definition value null
security: property package.definition new value com.sun.javaws
security: property package.definition value com.sun.javaws
security: property package.definition new value com.sun.javaws,com.sun.deploy
security: property package.definition value com.sun.javaws,com.sun.deploy
security: property package.definition new value com.sun.javaws,com.sun.deploy,com.sun.jnlp
security: property package.access value sun.,com.sun.xml.internal.ws.,com.sun.xml.internal.bind.,com.sun.javaws,com.sun.
deploy,com.sun.jnlp
security: property package.access new value sun.,com.sun.xml.internal.ws.,com.sun.xml.internal.bind.,com.sun.javaws,com.sun.
deploy,com.sun.jnlp,org.mozilla.jss
security: property package.definition value com.sun.javaws,com.sun.deploy,com.sun.jnlp
security: property package.definition new value com.sun.javaws,com.sun.deploy,com.sun.jnlp,org.mozilla.jss
basic: Applet geladen
basic: Applet resized and added to parent container
basic: PERF: AppletExecutionRunnable - applet.init() BEGIN ; jvmLaunch dt 210124 us, pluginInit dt 911257 us, TotalTime: 1121381 us
basic: Applet initialized
basic: Applet made visible
basic: Starting applet
basic: completed perf rollup
basic: Applet started
basic: Told clients applet is started
==== JavaSound Minim Error ====
==== Don't know the ID3 code APIC

==== JavaSound Minim Error ====
==== Don't know the ID3 code APIC

==== JavaSound Minim Error ====
==== Don't know the ID3 code APIC

==== JavaSound Minim Error ====
==== Don't know the ID3 code TOFN

==== JavaSound Minim Error ====
==== Don't know the ID3 code TDEN

==== JavaSound Minim Error ====
==== Don't know the ID3 code TDOR

==== JavaSound Minim Error ====
==== Don't know the ID3 code UFID

==== JavaSound Minim Error ====
==== Don't know the ID3 code WCOM

==== JavaSound Minim Error ====
==== Don't know the ID3 code WOAF

==== JavaSound Minim Error ====
==== Don't know the ID3 code WOAR

==== JavaSound Minim Error ====
==== Don't know the ID3 code WOAS

==== JavaSound Minim Error ====
==== Don't know the ID3 code WPAY

==== JavaSound Minim Error ====
==== Don't know the ID3 code WORS

==== JavaSound Minim Error ====
==== Don't know the ID3 code WPUB

I have a hunch why the export was misbehaving.  Apart from the problems with size() (which from a quick test don't look like they should have caused it to fail; though should still be avoided) it looks like Processing treats the first tab of a sketch as 'special'.  When you add new tabs the first tab stays as the first and the remaining tabs are sorted alphabetically after it (that sorting annoys me sometimes - I'd like to be able to re-order them manually).  Anyway - I suspect there's a good reason for this...

In your case your first tab contained a class definition rather than what I'd normally expect to see - i.e. at the very least a setup() call.  I just copy-pasted the code around so that your Spielfeld code (including setup()) is on the first tab and now the HTML export is picking up the sketch size correctly...  So I suspect that was the only thing stopping the export from working properly, and even then it was probably just a matter of editing the HTML...

My hunch is that setup() should always be on the first tab - at least if you plan to export for web...