New Ideas

New Ideas to Akihabara engine

Add a new file with development utilities like: FPS, main screen skip and so on.
A new tool to merge all images into a single sprite and generate a bundle file to improve game files download.
Minify all Akihabara files and merge then into a single one (just need to think about optional files like help.js)
Remap buttons to not use A,B,C to the end user, using the right keys of his keyboards mapping to this buttons

Make the games bookmarklets with icons in order to run fullscreen on iOS and webclip-compatible devices (suggested by Sblargish)
Add a parameter during game initialization (i.e. help.akihabaraInit({...}) in order to specify the default debug font path.

Particle engine with fast performances (example: http://jarrodoverson.com/static/demos/particleSystem/)
Server technology aware networking layer

Split akihabara files. Something like this:
- akihabara.js
- akihabara.platformer.js
- akihabara.topview.js
- akihabara.shmup.js
- akihabara.tools.js (We will use this file to put some things from toys and help that are not from a game type specific. We just need to be careful to not create a new help.js)
A new way to define counters to have a default counter, so, the developer don't need to care with this counters by default, but is still available to change if necessary.
A good documentation with a documentation generation based on code comments that works good (not only technically, but using a way that we feel comfortable to add it).
A deploy tool to minify all files and generate a akihabara.engine.js.min to put on production environment
A key remapping to avoid confusions to the end user.
Some boilerplate page to start a game, with some good tags.
A plug and play mouse/touch support