Actually, it depends on what you want. Running the PDE and making it to load the sketch is probably slower (at least on start up time) than running an exported application.

BTW, I am a bit surprised by your statement (running slower) but then again, I don't know how exactly the exported application runs (JVM parameters, etc.).

An intermediate solution might be to export to Web, to get a couple of jars. Then you can run the application with a simple .cmd file (or .bat if you are old school).

I was just testing (with the AnimatedSprite example, having a data folder) what I write with Processing 0191 (just after 1.2.1) and I see they export now with Processing classes in the main jar, there is no longer a core.jar. Anyway, putting:

1. java -jar AnimatedSprite.jar

in the .cmd file should run the applet. If you have a core.jar, it should look like:

1. java -cp core.jar -jar AnimatedSprite.jar

If there are other jars (libraries), just add them after core.jar, separated with semi-colon (colon on Unix-based systems).

You can add other parameters, like memory settings (can act on speed), to the command line.

I'm also unsure as to why the sketch runs faster from within processing compared with as an exported application. It uses JMyron for webcam capture and Minim for sound so maybe these libraries have something to do with it?

I'll have a go at running the jars from the command line, although i'm having trouble with the syntax at the moment but will report back. I think though I will have the same problem as when running as a standalone app with regards to the performance reduction so still want to hear if anyone knows how to run a sketch from processing through the command line.

Cheers.