Here are a few things I’ve learned, I’m working with Frobtads (I know, you Inform heathens, “groan…”):
- FrobTads has a “plain,” text only mode, possibly handy for ‘regex’ redirection based on message type (room name, descriptions, objects, etc.)
- Frobtads has a handy sample game, sample.t, for testing
- Several helpful plugins exist for listing exits, objects, etc.
Overall I think a plugin could be constructed that “borrows” from these plugins to create output that is robust for writing regex expressions to “pull out” the data bound for the e-ink display from the prose.
This means that the ‘eink.t’ plugin needs to be compiled into all games using the compass–you unfortunately cannot just run games with the compass “out of the box.” Fortunately, putting in an “#include eink.t” line and recompiling isn’t a big deal.
Incidentally, the UNIX/Linux Tee command may be used at invocation to pipe output to both the screen and (after regex) the e-ink python library bound for the e-ink display.