It is clear that I am struggling to do all the coding that is needed. And it is unnecessary, because clearly we have skilled people on these forums that can develop new features to Pokitto on their own.
Therefore I am going to start opening the Simulator code to all of you as soon as I get back home.
Things to do…
make sound work on all OS’s
tiled graphics modes
128x128 “Pico 8” mode
tinyArcade mode (96x64@256 colors)
220x176@16 color mode (yes, it is possible, although needs lotsa RAM)
file selector (in progress)
Menus & virtual keyboard
graphics style improvement, getting rid of legacy limitations
simulate I/O’s with console prints and/or button inpus as digital inputs
Pico-8 would be an excellent idea! A lot of great games:-)
I just hope that scaling of Pico screen to the native Pokitto resolution do not affect too much to the quality of the graphics.
Pico-8 gives people more reasons to purchase Pokitto, and there is still hi-res native mode for making high quality Pokitto games too. That is a bit like playing Wii games on WiiU until the native game library is good enough for selling the device alone.
The pokitto screen probably matches the simulator 220x174. I think that having the 128x128 screen 1:1 pixel centered, then the possibility of adding a border graphic of some sort, like the super gameboy? That would be cool. It could probably be done without taking up much RAM by direct pixeling from a pico8.bmp on the MicroSD card?
Wow. This is getting really interesting. In order to allow maintennance to work across all systems, I need to link the github repo to mbed repo and possibly split the repo into submodules… hmmm…
Edit: explanation: the hardware target uses exactly the same core as the sim. I want to maintain the core so that no matter if you work on sim, hardware or on online mbed IDE, the core is always up to date.
Edit2: this is not a problem, its just setting up things in the right way.
Edit3: but it means the core should be its own submodule