Posts Tagged ‘applet’
10 hours to go, and I generally finished the interface, including a nice message parser, an inventory screen, pause and about screens, and winning and losing screens.
I have almost all the minimum features that I wanted, and at least all the features required for the game to be completeable. So I guess I will take a quick break, and add some content.
I’m pretty sure I won’t be able to add all the sounds, music and art I wanted to, but I’ll see how much I can get done. If I’m lucky, I might even sneak in one more feature or two.
10 hours to go, fight, fight!
Due to the fantastic packaging advice post now stickied to the page, I created a web applet wrapper for my game so that it could be played in browser, for those who don’t want downloads cluttering up their desktop.
I tested it in Chrome and in Firefox, please let me know if another browser is having trouble.
It is a little buggy because it is just a wrapper and is still trying to process the executable code, had I had this in mind from the start I could have segmented it better. Something to keep in mind for the next one.
After finishing my game I noticed that I had plenty of spare hours left so I decided to add a scoreboard. Unfortunately that meant communicating with a web server, which to my knowledge meant I had to sign the thing.
Signing applets involves some console work, but most importantly it involves an annoying popup asking people to let the thing run. In my mind that’s nearly as bad as a installer and I didn’t want anything of the sort, besides I tried that on a previous project (which come to think of it was also a 48 hour game) and that resulted in people not playing it a all.
From some android work I’ve done I remembered I can call links to pages even if the app has no permissions(the browser handles the links), and I wasn’t too surprised when I found out that an unsigned applet can do the same.
Basically what I did was call
(processing function, no Idea if it’s the same in reglar java) where ‘asdfg’ was an encrypted version of the score. This coupled with making each score unique prevented floods on the scoreboard.
The function spawns a popup window, and I’ve noticed that even if chrome blocks it, it still preloads the score page causing the score to go through. This may or may not be a security issue.
If anyone knows a better, or just different way to have an applet share its internal data I’d love to hear it.