Talk:Terminal control/Positional read: Difference between revisions

terminal mode and terminal queries
(terminal mode and terminal queries)
Line 13:
:::: I use a terminal-mode IRC client (as opposed to a GUI one such as XChat) for detachable sessions, speed and portability. While detachable, VNC, nx and RDP would all be slower than a terminal over SSH (I contend this would be true of any flexible remote console involving raster imagery), and I can find a terminal emulator for whatever platform I'm using. --[[User:Short Circuit|Michael Mol]] 13:57, 19 October 2010 (UTC)
::::: Ok, but some (perhaps most) of the current terminal control implementations, here, on Rosetta, do not support that kind of terminal. But also, if I were building the kind of application you are now describing, from scratch, and I wanted to support use by a lot of people, I think I would implement it to support ajaxy web browsers (mostly on localhost), and mobile phones. --[[User:Rdm|Rdm]] 15:47, 19 October 2010 (UTC)
 
I love terminal mode programs - and I don't think it is a mistake to implement them on modern operating systems. They are fast, efficient, easy to automate, accessibility friendly and it is possible to extract data from the screen for use in other programs. I don't know what attracts people to slow and manually operated graphical systems, rather than efficient terminal mode data entry systems. I am shocked at the lack of information about terminal control in the various programming language manuals. Being able to maniplate the terminal display is a fundamental operation IMHO.
 
[[User:Markhobley|Markhobley]] 23:38, 19 October 2010 (UTC)
 
I vaguely remember looking at that terminal query problem on Unix. From what I remember, a query for a character at a specific location is resolved by the terminal driver (which maintains a buffer).
 
[[User:Markhobley|Markhobley]] 23:38, 19 October 2010 (UTC)