I've unearthed one of my old pull requests and now we can (finally!) have proper Python games on the NumWorks calculator. The missing bits were keypad readout and some basic graphics primitives (zardam's time module was already merged some time ago). I've scrambled together a Pong game to showcase this:

Drawing performance is honestly quite terrible because the framebuffer isn't memory-mapped, but it's enough for a smooth Pong and probably other basic games in real time. Redrawing the full screen on each frame would require drawing the entire screen in one go pixel after pixel (like the third-party firmware GESTE did), not unlike racing the beam on the Atari 2600, but doing that from within MicroPython would be challenging.
Sources:
Drawing performance is honestly quite terrible because the framebuffer isn't memory-mapped, but it's enough for a smooth Pong and probably other basic games in real time. Redrawing the full screen on each frame would require drawing the entire screen in one go pixel after pixel (like the third-party firmware GESTE did), not unlike racing the beam on the Atari 2600, but doing that from within MicroPython would be challenging.
Sources:
- https://tiplanet.org/forum/viewtopic.php?t=22284&p=239419#p239388 (News on TI-Planet)
- https://tiplanet.org/forum/viewtopic.php?t=22286&p=239396#p239396 (Initial post on TI-Planet)
- https://github.com/numworks/epsilon/pull/746 (pull request for NumWorks)
- https://workshop.numworks.com/python/jblbeurope/pong (Pong source code)