CompuServe Messages

No, I'm not. I've written several _very_ complete terminals, some that were emulations and some that were actually hardware terminals, no other purpose in life. I maintain that you _must_ keep a record around of what is in the screen – maintaining things _only_ in a bit map is an extremely shortsighted thing to do. If you choose that, you can't: Print screen Cut/paste _temporarily_ hide portions of the display cursor around the screen attach "action" attributes (Like blink, register-shift…) local edit without going to "hacks". Like command line buffers. Like SnipIt. Like SuperBitmaps (Great, but costly in memory) like special attribute maps, and as for local editing, only on the current line. Line oriented displays are OLD tech. Screen oriented ones came in years ago. Not that I'm a fan of the keyboard, but if I _have_ to use the darn thing, I don't want to use a "glass teletype". I'm not wrong. You haven't thought it thru, is what, I think. I've never said that ONLY text is what you want. We need what we have, AND the internal availability of a textual/attribute record so we can work with it, too. Furthermore, that record should be accessable to external programs. And as I have said before, in term of performance – I know what I'm talking about. I've been quite deep into graphics, into terminal and terminal emulation design, and the Amiga console isn't all that hot. I could fix it – if I had the source. –Ben–