Text-based user interface: Difference between revisions

Content deleted Content added
m Reverted 1 edit by 174.251.168.127 (talk) to last revision by 77.13.65.39
Ckindel (talk | contribs)
Updated to reflect modern Windows Terminal stuff.
Line 25:
== Under DOS and Microsoft Windows ==
[[File:Fdedit.png|thumb|300px|The [[FreeDOS]] Edit user interface]]
On [[IBM Personal Computer]]s and [[IBM PC compatible|compatibles]], the Basic Input Output System ([[BIOS]]) and [[DOS]] system calls provide a way to write text on the screen, and the [[ANSI.SYS]] driver could process standard ANSI escape sequences. However, programmers soon learned that writing data directly to the [[screen buffer]] was far faster and simpler to program, and less error-prone; see [[VGA-compatible text mode]] for details. This change in programming methods resulted in many DOS TUI programs. {{anchor|Windows}}The [[win32Windows console]] environment is notorious for its emulation of certain EGA/VGA text mode features, particularly random access to the text buffer, even if the application runs in a window. On the other hand, programs running under Windows (both native and DOS applications) have much less control of the display and keyboard than Linux and DOS programs can have, because of aforementioned win32Windows console layer.
 
[[File:itmouse.png|thumb|300px|left|Mouse cursor in [[Impulse Tracker]]. A more precise cursor (per-pixel resolution) was achieved by regenerating the glyphs of characters used where the cursor was visible, at each mouse movement in real-time.{{citation needed|date=December 2011}}]]
Line 33:
Some notable programs of this kind were [[Microsoft Word]], [[DOS Shell]], [[WordPerfect]], [[Norton Commander]], [[Turbo Vision]] based [[Borland]] [[Turbo Pascal]] and [[Turbo C]] (the latter included the [[conio.h|conio]] [[library (computer science)|library]]), [[Lotus 1-2-3]] and many others. Some of these interfaces survived even during the [[Microsoft]] [[Windows 3.1x]] period in the early 1990s. For example, the [[Microsoft C]] 6.0 compiler, used to write true GUI programs under [[16-bit]] Windows, still has its own TUI.
 
Since its start, [[Microsoft Windows]] includes a console to display DOS software. Later versions added the [[Win32Windows console]] as a native interface for [[command-line interface]] and TUI programs. The console usually opens in window mode, but it can be switched to full, true text mode screen and vice versa by pressing the [[Alt key|Alt]] and [[Enter key|Enter]] keys together. Full-screen mode is not available in Windows Vista and later, but may be used with some workarounds.<ref>[http://social.technet.microsoft.com/Forums/en/w7itprohardware/thread/3cc6994e-cbc2-4844-b040-a3c8385c69a5 cmd prompt full screen in Windows 7]. Social.technet.microsoft.com. Retrieved on 2013-06-15.</ref>
{{-}}
 
[[Windows Terminal]] is a [[Tabbed|multi-tabbed]] [[terminal emulator]] that [[Microsoft]] has developed for [[Windows 10]] and later<ref>{{cite web|url=https://www.theverge.com/2019/5/6/18527870/microsoft-windows-terminal-command-line-tool|title=Microsoft unveils Windows Terminal, a new command line app for Windows|first=Tom|last=Warren|date=May 6, 2019|website=The Verge}}</ref> as a replacement for [[Windows Console]].
 
The [[Windows Subsystem for Linux]] which was added to [[Windows]] by [[Microsoft]] in 2019, supports running [[Linux]] text-based apps on Windows, within [[Windows console]], [[Windows Terminal]], and other Windows-based terminals.
 
== Under Unix-like systems ==