Right, I'm probably going to ignore the audio issue, and plough ahead regardless.
The audio tweaks can be made in the future. After all, this engine is 100% javascript, so everything is really easy to tweak afterwards, unlike most of my normal games that require recompiling and reuploading and then the player to realise there's an update, and redownload it.

-=-=-

Today's tasks are as follows.

1. End Game
I need to ensure the game knows when it's been complete, and gives some kind of fancy "Well done!!" notification or something.
It currently doesn't.
In order to test such a thing, I'm definitely going to have to add a test/cheat mode into the game, because .. I'm not actually very good at it!!

2. Scoring
There's currently no scores in the game. I'm not sure how other people handle scoring in Solitaire games. Perhaps a little more "testing" is in order *cough*plays Microsoft Solitaire for a few hours*cough*

3. Menu System
If the intention is to add oodles of card/board games into the engine, then the engine's going to need a nice sturdy frontend, and .. Oh god, a Menu!! Aaargh!!

4. Possibly add a second game..
Assuming I can get everything "finished" for Spider, it might be a good idea to attempt to add a basic Klondike solitaire, too. That'll certainly stress test the multi-game abilities of my functions!



Before getting stumped by the evil Audio issues, I did at least manage to add a Portrait mode for Phone users.
The portrait mode currently insta-switches to the new "Large-Print" cards, and squishes everything down into a slightly more manageable area.
Hopefully these changes are enough to combat the earlier "Too small" issues that were present.