Just a quick heads up; I got sick of running tf under screen, and have started work on a web front-end to TF (codename WTF until I think of something better). With the current code, stdin/stdout are redirected to a single telnet or websocket connection (new connections disconnect clients). Working reasonably well for me at the moment, and includes a lighweight built-in webserver.
The direction I'm planning on taking is adding GMCP messages to reflect TF variables, so that TF can run permanently on under a shell account somewhere, and ad-hoc browser connections allow play with a simple GUI.
Is this something that other people would be interested in?
Phil
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Hi all,
Just a quick heads up; I got sick of running tf under screen, and have started work on a web front-end to TF (codename WTF until I think of something better). With the current code, stdin/stdout are redirected to a single telnet or websocket connection (new connections disconnect clients). Working reasonably well for me at the moment, and includes a lighweight built-in webserver.
The direction I'm planning on taking is adding GMCP messages to reflect TF variables, so that TF can run permanently on under a shell account somewhere, and ad-hoc browser connections allow play with a simple GUI.
Is this something that other people would be interested in?
Phil
There's already a GMCP patch out there.
http://mikeride.chaosnet.org/abelinc/scripts/index.html
I've integrated it with some others here:
https://github.com/warmstarter/tinyfugue-1