It seems like unexpectedly terminated tasks prevent the workqueue from being released. It's a silly screwup, but I'm going to convert the servlet into an applet, because the server is running at 100% for 1-2 minutes, per shrink...

Hi, appreciate more people! Σ ♥ = ¾Learn how to award medals... and work your way up the social rankings!

How it works: I recently moved the service to a few hundred of EC2 instances. Every time you submit a peice of sourcecode, it will analyse its structure and simulate it's output, with certain keyboard/mouse inputs. Using these statistical results, it will generate random sequences of bytes, and will perform the same process. Once the results of these two match up, we found an equal application. Then we wait until we receive at least 8 results from the cluster, and simply pick the smallest. It costs about $0.17 per shrink, so please keep that in the back of your mind.

Now off to convert this to an applet!

Hi, appreciate more people! Σ ♥ = ¾Learn how to award medals... and work your way up the social rankings!

How it works: I recently moved the service to a few hundred of EC2 instances. Every time you submit a peice of sourcecode, it will analyse its structure and simulate it's output, with certain keyboard/mouse inputs. Using these statistical results, it will generate random sequences of bytes, and will perform the same process. Once the results of these two match up, we found an equal application. Then we wait until we receive at least 8 results from the cluster, and simply pick the smallest. It costs about $0.17 per shrink, so please keep that in the back of your mind.

You have a warped sense of humor.

Quote

Now off to convert this to an applet!

How can an applet execute the compressor utilities (external executable programs)?

How it works: I recently moved the service to a few hundred of EC2 instances. Every time you submit a peice of sourcecode, it will analyse its structure and simulate it's output, with certain keyboard/mouse inputs. Using these statistical results, it will generate random sequences of bytes, and will perform the same process. Once the results of these two match up, we found an equal application. Then we wait until we receive at least 8 results from the cluster, and simply pick the smallest. It costs about $0.17 per shrink, so please keep that in the back of your mind.

Now off to convert this to an applet!

That is insane! So do you test each pixel of output between every test program?

How long would it take do do a 16k LWJGL one, 4 times the cost or ^4 ?!

How it works: I recently moved the service to a few hundred of EC2 instances. Every time you submit a peice of sourcecode, it will analyse its structure and simulate it's output, with certain keyboard/mouse inputs. Using these statistical results, it will generate random sequences of bytes, and will perform the same process. Once the results of these two match up, we found an equal application. Then we wait until we receive at least 8 results from the cluster, and simply pick the smallest. It costs about $0.17 per shrink, so please keep that in the back of your mind.

Now off to convert this to an applet!

That is insane! So do you test each pixel of output between every test program?

How long would it take do do a 16k LWJGL one, 4 times the cost or ^4 ?!

I hope to get it online later tonight. Basically, I bruteforce the splitsizes in kzip and bjwflate. With 7z you simply have to be lucky as it doesn't have any interesting commandline parameters. The proguard configuration files are trivial. I don't get why you wrote those massive files, you're asking proguard to remove dead code... Can't you do that yourself? I never wrote String.indexOf() and ignoring its return-value, without it resulting in major problems (I needed that indexOf, so ignoring it broke something else)

Hi, appreciate more people! Σ ♥ = ¾Learn how to award medals... and work your way up the social rankings!

Run ant in the base unzipped directory to setup your environment (download jars and make sure properties are setup right).

Then, modify the "sample-game" directory structure to include your source Java file in the "src" sub-directory, and setup the project.properties file. Then, you can run "ant" from in that directory to build all the jar files, which are output into the work/jars directory.

It takes a long time to run, because it performs many iterations over different combinations of class file shrinking and compression.

java-gaming.org is not responsible for the content posted by its members, including references to external websites,
and other references that may or may not have a relation with our primarily
gaming and game production oriented community.
inquiries and complaints can be sent via email to the info‑account of the
company managing the website of java‑gaming.org