> >> If possible, it would be nice, if you could insulate the emulation
> >> layer, so that we could write other emus as need arises, e.g. a
> >> Linux-console-emu or a vt100 emu etc. Should be pretty
> >> straightforward - just a few interfaces for I/O and blitting fonts.
> I thought about that too, but unfortunately I don't have the time to
> work out all the details.
Get a snapshot of EvStack. We had such a system in place, there. Contains
an xterm-compatible parser IIRC.
> For example, some terminals save scrolled lines, some don't (so where
> do you store screen information).
We have taken care of this by a module we called "scroller" IIRC.
> Most of them implement a huge common subset of commands, and so on. So
> let's do the following: let me finish this one (I'm really enjoying
> working in cmtt10!) and post it on sourceforge, then other people can pick
> it up and "generalize it".
Sure.
> As an aside, do you people really see the need for a completely generic
> terminal? What are the reasons for a `linux' terminal emulator not being
> enough, for example?
umm *grin* - I'd like to show the kernel people once more, that a tty
layer can be done nicely and modular ;-)).
> Ah! I need a good, unused name, for this thing. I am calling it
> "therm" right now. I don't think it's bad, but my imagination dried up
> a few projects ago ("dviv", "psv", oh well).
Hmm - aemu (Ansi EMUlator), atemu ( Ansi Terminal EMUlator), ATE (Ansi
Terminal Emulator), TEA (Terminal Emulation: Ansi), AGATE (Another
GGI ANSI Terminal emulation) ... just some thoghts ... ich can be pretty
creative.
Give me a "theme" or "mindset" and I'll try to find a few more ...
CU, ANdy
--
= Andreas Beck | Email : <[EMAIL PROTECTED]> =
