I’ve been encouraging everyone make “the middle” bit based around RemGlk. The main absent things currently in RemGlk is 1) Glk style hints / text colors for Z-machine stories, 2) Glk sound support. I’ve had moderate success with adding style-hints to RemGlk - and I’m hoping audio will be done for me Performance wise, there is little reason to not use RemGlk - the overhead of going from Glk to JSON is very low - and it makes debugging Glk far simpler than something like the topic we are reading ( David Fletcher’s Qt Glk
Why did I come to Qt this past week? Because I started out following the approach Twisty 2.0 & Son of Hunky Punk were taking to back-end game engine, but ultimately I really got bogged down in how poorly the Android framework deals with console input/output (as in stdin and stdout). I’ve mostly solved these issues, but it took months of testing on a lot of different phones and tablets - and is still not as stable as I would like. I’m faced with a pretty messy code base now (in Java) and starting a rewrite… but now I"m considering outright moving to Qt for the back/middle and continue to encourage multiple front-ends be developed that trade JSON. (Thunderstrike is an app example of an independent front-end consumer app of JSON, and someone could make a GlkOte app that interfaces with the JSON - which is what is already basically available here: github.com/erkyrath/remote-if-demo - a GlkOte that uses JSON via RemGlk).
I know nothing at all of QML and it looked like a pretty steep learning curve, with XML layout files that get compiled and such that quickly reminded me of Android’s native layout system. If someone wants to make a RemGlk QML front end… please do! At this point, I feel like nobody else has shown much interest in jumping on the JSON RemGlk bandwagon… but I keep making noise of this key architectural change.