Show HN: HTerm, The Graphical Terminal for iOS, MacOS and Linux
41j.com
41j.com
It also lets you render PNG graphics inline by streaming it as base64 encoded data. Which I find handy for displaying email attachments from mutt.
It's open source, and a iOS version is available for 99c (though you can also compile it yourself of course). I hope to make a Cydia version available if the project gets any traction.
At this stage I'd love feedback, bug reports and of course users to push me to do more development.
You mentioned the VK100 as the original ReGIS graphics terminal which I'm fairly sure is correct. It might be worth mentioning that terminal's more familiar name, the "GIGI". It actually came out a fair bit sooner, certainly earlier than '85. I'm pretty sure I was working in a lab stuffed full of them in '82, '83 at the latest.
They were a pretty fun terminal to work with. Among other things, they supported the ability to upload bitmap fonts. A friend of mine put together a "Rogue Font" which put those terminals in demand in our lab for playing "rogue". I did a multi-terminal chess board system for them.
ReGIS was supported in later DEC terminals, the VT-240, VT-300 etc. By that time I was working in the TBU's (Terminal Business Unit) QA group which was '85 and on. That was the same era that DEC released their first PostScript based printer (the LPS-40) not too long after the Apple LaserWriter came out. It was a fun time for early computer graphics.
The ReGIS support I currently have is pretty basic, mostly just designed to support gnuplot line graphs. If you have any old code that generates ReGIS graphics I'd LOVE to see it.
Could access that path, but found: /anon/public/decus/vms/library/v00365
Looks great! All fortran 77 code by the looks of it, will certainly be something fun to play with, thanks!
In addition, it looks like you use a plain-ASCII inline sequence to signify the start of image/media data. I think Terminology uses a special escape sequence to begin its media rendering, and that seems like a more robust approach which you might want to consider; echoing ASCII text to a terminal should probably stay as ASCII when rendered, imo.
I'll have to ping them and see which escape sequence they use, would be great to use the same ones. I'll have to dig into terminology a bit more, I think we have slightly different design goals though. My main requirements were "no server side support required" and "works when bouncing ssh across multiple boxes". It looks to me like they're either rendering local content, or require a special toolset to be installed serverside (which I wanted to avoid as I bounce between lots of different client machines).
Can you provide a generic binary?
https://github.com/new299/hackterm
Though the source needs quite a lot of work!