Friends:
GPOR
IndieVault
In the last few days i went back to my little HTML5 engine that i used for a contest this summer, resolved a pair of bugs and made a little game to test if it works well, ora at last decently, on Safari mobile on an iPad (version one).
Many people say that the iPad is a good platform for card games, so i made a classic solitaire card game!

In the last weeks we moved Alakrom on a new server, corrected many bugs, but the most interesting thing has been the map editor. Thanks to the new map editor we don't need to write maps "by hand" anymore, so probably you'll se many more maps in the future :)
Here's a video preview of the map editor:
During the last month, in the free time (what?!?) between a debugging session on Alakrom and the new match visualizer for Foosball Manager, we experimented a bit more with Html5 and the Canvas element.
We have a working version of alakrom, there are only 4 unit types, one map and some bugs...but...it works! Here's a video of a "live" match between the two Splashgrapes guys, only some turns, not the entire game, just to show you how it's working. Enjoy!
The development of Alakrom was stopped some time ago, but now we finally have time to work on it again. The server code is almost finished, it's just a matter of debugging. The client side code is working too, it uses the nice MooTools javascript library to show off things and handle user input. There's no need for Flash plugin.
We're now trying to find a good graphic style for the game. We'll leave you for now with a screenshot of the game as it is now:
Finally back working on games! We are now focusing on the fresh new HTML5, learning all the features an writing a basic game engine, based on the canvas element, which will be used for the client-side part of some of our projects.
At the moment HTML5 is not as popular as Flash, and there are many compatibility and performance problems with different browsers, but in a future perspective it can be a good choice.
Nowadays browser engines are improving constantly, both in compatibility with standards and javascript performance. Even the future IE9 seems to be going to be html5-compliant.