I should probably try to finish off Blockman in the Browsercade, today, but I'm slightly worried that there's a teensy bit of slowdown in the engine, so I think today's plan should probably be to track that down.

I've had to add a limit to how many hexes I'm drawing on the Petit-Switch screen at once!!

Alan suggests

Looks pretty good. I did spot a slight half-pixel seam where the background wraps around. I like the parallax effect, though.
I've cheat-fixed that for the meantime, by simply wrapping the buffer a single pixel closer to itself, but it might look more glitchy once I start doing different types of backgrounds.
I need to add a "sprite to buffer" function, to check that, though.

1. People seem utterly baffled by the start-screen of Browsercade.
I put that there, because a lot of browsers need a single click before they initiate any audio, but seemingly people are instead "waiting" for it, and think the thing's broken.
D'oh!!

The gradient background in the above screenshot has been drawn to a secondary canvas, which is then redrawn onto the main canvas.
This seems to work reasonably well, and should hopefully allow for a fair number of generated backgrounds and other such effects, without requiring huge 1024x1024 background images to be downloaded.
The whole thing runs a little slowly on my Samsung Galaxy 10 A, however, so I'm going to have to add an option to disable the buffer when necessary.
But otherwis...

In order to properly test my onscreen touch controls, I'm going to need some kind of quick playable game, so that's going to be today's task.
Something short and simple, but complex enough to really put the controls to the test.

-
I'm fairly content with how the touch controls seem to be working, now, and they're apparently functional on both iPad Wide and iPhone Tall displays.
The DPad can be a teensy bit large on iPad Tall, though, so I might yet still make an optional thumbstick mode instead.
Simple testing has been done on the menus, but "real world" testing won't be happening until there's a "real world" game to test it with.

Crikey, I wasn't expecting this to be as hard as it is!
Reminder to developers : Just because it works with a mouse on your PC, doesn't mean it'll work well with a giant iPad screen or tiny iPhone screen, directly in your hands!
I think the rest of today will probably be about shuffling the buttons on the screen, to try to find something that feels just right..
Also, I might try making an analogue thing, instead of a dpad.

Started to make some progress with Touchscreen Controls, for Browsercade, today.
The hard part was getting this button to work..

I honestly can't fathom why Firefox's cache isn't doing what it's supposed to.

It's the little things..
Like how the game isn't saving highscores, and the onscreen scores aren't quite readable enough, and the music doesn't end during the game-over screen, and ..
The little things..
Still haven't actually coded the game, yet, either! This is all Framework stuff.

I think, today, I'm going to focus on getting the final Framework touches of Browsercade done.
Step One will be working out how plausible buffer-drawing is, whilst in a html canvas.

Step one, design (and/or copy+paste from previous editions!) a logo and icon for the game.
Step two, start writing game.
Step three, realise I'm a long way from being ready to start writing the game!!

I was almost certain I was near the end of the Browsercade Framework, but .. Nope.. There are still things to do!

I *think* I'm almost ready to start coding my first Browsercade game.

Looks much better!!
I'm now struggling with pausing the music when you alt+tab, or otherwise multitask away from the browser.
I seem to have got it working on iPad Safari (which is alarmingly unusual!) and Firefox, but not in Chrome or Edge.
The Pause screen's coming up, but the pause command doesn't appear to be triggering the pause event in the mod player.
Bit odd, but I think I've probably confounded my own code a bit, so will be double checking everything to be su...

Have spent today working on more menu gubbins, and default "Quit", "Retry" buttons and things. The basic pause screen is looking terribly familiar!

*phew*
Yeah, I knew that wasn't going to be easy...

Today I need to rewrite a ton of my input code, to work properly with redefined keys/gamepads, and then add a screen to let you do that.
.. More bloomin' menus.
Grrr!!

.. Have I said how much I hate doing menus?!

After a couple of days of back&forth, I've finally decided "meh, whatever!" and opted to go for a Coverflow-RipOff style menu.
It actually looks rather nice, and scrolls quite well, except on touchscreens where the thing's a teensy bit dodgy due to co-ordinate issues.
But otherwise it works nicely. (Although it isn't "quite" centring properly!)
Scroll around, select a game, sorted..
Currently all "games" lead to the exact same test engine, but eventually this will (...

Shoebox doesn't scale in a normal way.

I finally got music and sound effects working nicely together in the "not the shoebox" Javascript engine, and it all works nicely on my iPad, too!
Great stuff!!
Next Challenge.. Input!

@RSKGames suggests..
Can you consider making a version of the new AGAW JS mega compilation into an electron app so that you can retain the online scoreboard. In a electron app I think you can restrict users getting into the dev console.
I'll have a look into it.