mwm@eris.BERKELEY.EDU (Mike (My watch has windows) Meyer) (06/25/87)
In article <4074@jade.BERKELEY.EDU> spencer@eris.BERKELEY.EDU (Randy Spencer) writes:
<Figure, you got 8 meg of memory, but the 7.14 Mhz processor can't
<control 25 Word Perfects (and you would get lost in the screens), but
<if programs hid off in memory sleeping until a certain keypress they
<would be much better than Mac Desk Accessories. Imagine VT100 out
<there, ready to start at anytime with a simple keypress. Sure beats
<MockTerminal on the Mac.
How about an mg instead of a vt100?
Now that every one's talking about it, I might as well admit that I've
had a version of mg that sits listening on a port for a message
holding a file name. When it gets it, it does a WindowToFront and
issues a find-file for the user. You tell it you're thourgh with the
last outstanding edit request (exit-emacs, kill-buffer, or exit-server
commands), and it does a WindowToBack, and then an ActivateWindow on
the "next" window. Add a nice little 2K "edit" command that just talks
tothe port, and you're off and running. All works like a charm, and
makes editing Little SmallTalk code a *lot* faster.
It was while I was trying to fix things so that emacs window would
vanish that I ran into the "How much of the console device driver do I
need" problemds. Someday, I may get back to that.
I'd be interested in any efforts towards a standard in that area: say
a standard for what messages to the port "edit.server" should do, and
maybe what the device driver/library "editor.whatever" should do.
<mike
--
Here's a song about absolutely nothing. Mike Meyer
It's not about me, not about anyone else, ucbvax!mwm
Not about love, not about being young. mwm@berkeley.edu
Not about anything else, either. mwm@ucbjade.BITNET