This is interesting but over my head. I have an old Google Nexus 7 gathering
dust. Can I use it as an monitor for a Model T?
On Tuesday, January 19, 2021, 03:39:29 PM EST, Kenneth Pettit
<petti...@gmail.com> wrote:
I’ve actually stripped out the Model T logic from VirtualT and used the
framework for other apps twice now
Ken
Sent from my iPhone
On Jan 19, 2021, at 12:10 PM, Stephen Adolph <twospru...@gmail.com> wrote:
WRT using Virtual T - I just meant the framework. strip out Virtual T and
replace with a new application that uses all the same tool kit.
After all it is the only thing I know how to do!
On Tue, Jan 19, 2021 at 2:58 PM John R. Hogerhuis <jho...@pobox.com> wrote:
On Tue, Jan 19, 2021 at 11:44 AM Stephen Adolph <twospru...@gmail.com> wrote:
I am actually thinking about exactly that, a new VT100 app that implements the
custom M100 control codes, and takes serial data.Was thinking to use the
VirtualT framework to do it also.
VT100 is an industry standard so I don't know about M100 control codes. I think
you had mentioned something about arrow keys being different in the current
implementation. Which control codes are you referring to? The whole set of
Model 100 escapes?
Which is fine... that's one way to go and it can be implemented exactly. It
just isn't VT100.
The other issue is encoding and fonts. HTERM does this mapping on the Model T
side, which makes it compatible with any shell/terminal. But you could also do
a mapping to Unicode on the terminal side. Then you could use off-the-shelf
fonts.
Another way to go would be to render the display completely yourself with
graphics based on the Model 102 character set. Then you could get very high
fidelity.
As to VT, it's just a terminal, so you don't need 99% of what VT does. And what
VT does do that you need, like rendering the display, has to pass through the
Model T ROM and 8085 emulation. And it's limited to 40x8. Seems like it creates
more problems than it solves. Just displaying character bitmaps to the screen
is a simpler task.
-- John.
