jojoe

Any reason why you wouldn't want to use "onload"? That would certainly allow you to open that link without the need for additional user input.

Your pathfinding is somewhat broken, methinks (takes way too long for the repositioning to kick in).

I had similar issues when I first tried the pathfinding behaviour but, eventually, fixed them.

Could you upload the .CAPX?

Should be possible.

Requires some Javascript Magic though.

In theory, you could simply listen for every single key on that keyboard.

The thing that is currently unworkable though, is getting the browser to interface with any input device that isn't a keyboard or a mouse.

There's already a draft for MIDI support though (http://www.w3.org/TR/2012/WD-webmidi-20121025/) and someone has already laid some groundwork for MIDI keyboard integration.

See here:

abumarkub.net/abublog

and here:

abumarkub.net/abublog

SO yea. No native support for MIDI keyboards yet, though this might change soon and then it really will be just a matter of implementing simple event listeners (if at all).

To be fair, PNG for websites isn't the most efficient choice anyways.

As far as first impressions go, JPEG is still king.

Likewise, SVG is pretty pointless as well. Rendering every single asset in realtime takes way too much CPU time away from ingame logic.

Adobe Flash got away with it, since they had their own proprietary rendering API which rendered SVGs much more efficient than any browser does.

Does that mean people are finally able to anticipate the performance of a Windows 8 app without "upgrading" to the abomination that is Windows 8?

I've a question for the Blackberry RIM aficionados.

Will the "old" Playbook be updated to Blackberry OS 10 or will people be required to lash out 500 quid for the 3G+?

I'd also be interested in how well Construct2 made HTML5 games run on a Playbook. Is the hardware powerful enough for serious WebGL action?

jojoe

So how is pathing going to work with that?

Will it be possible to group similar tiles into groups and adapt certain collision points to all of them?

I'm not sure this is possible yet, but it would be great if there was a way to let pathfinders detect a certain colour range and class all pixels matching the colour range to solid.

Clyde also seems like it could end up being a great game.

Other than that: Blight, Schr?dy, Courier, Super Ubi Land, Loot Pursuit, 8Bit Boy, Mortar Melon ...

Quick update.

Buttons do work fine now. I switched to the standard OnClick action and disabled touch emulation. Touch actions are still a horrible mess. Depending on where I place them, they're either slower (sprites) or don't work at all (buttons).

Audio is still not working though. I slightly altered the function querying the browser for OGG compatibility. While this did work with IE9 and an MP3 file, I can't quite get it to work with .WAV and my HP Pre 3.

I can't speak for CocoonJS (though I do think that launcher app is simply to get development started), but that's how it works with Phonegap Build.

1. Create the game

2. Add a description, author and name of the game.

3. Export to Phonegap via Construct 2's exporter

4. Zip all the contents of the exported folder

5. Sign in with Phonegap Build.

6. Upload the zip folder

7. Click "Build"

8. Download whatever file you need (APK for Android, IPK for WebOS, etc)

9. Play the game

In order to sign the APK for Android you either need to unpack the APK and sign it yourself (if you don't know whether you can trust Adobe or not) or, preferably, add the key to your Phonegap Build profile before upload.

Here's the whole gist about signing an Android app.

build.phonegap.com/docs/android-signing

Well. If it's not an utter disaster, it sure will be a great opportunity for those who can't afford to buy the overly pricy 1st party dev kit and sign several NDAs with Nintendo.

I wish Sony would support HTML5 for it's Playstation Mobile developer program.

Well. If you're looking for the most straight-forward solution, you can't go wrong with CocoonJS' cloud service, the Intel Appmobi XDK or Phonegap Build.

My personal favourite is Phonegap Build, which doesn't even require any additional software. Just sign-up with them or sign-in with an existing Github account, upload a zipped folder with all your files and press "Build".

Supported platforms: Android, iOS, WebOS, Bada, BlackberryOS 5/6/7, Symbian and Windows Phone 7.

In addition to the aforementioned platforms, the regular (offline) Phonegap also supports Tizen and Windows Phone 8, but requires quite a bit more work.

As for suitable devices: it very much depends on what OS you want to implement with and how much money you can spend.

For Android, I'd suggest either the Google/Asus Nexus 7 (powered by the purest Android Jellybean) or an Amazon Kindle Fire HD/Nook (both quite affordable).