curses (programming library)

curses is a terminal control library for Unix-like systems, enabling the construction of text user interface (TUI) applications.

The name is a pun on the term “cursor optimization”. It is a library of functions that manage an application's display on character-cell terminals (e.g., VT100).[1]

Overview

Using curses, programmers are able to write text-based applications without writing directly for any specific terminal type. The curses library on the executing system sends the correct control characters based on the terminal type. It provides an abstraction of one or more windows that maps onto the terminal screen. Each window is represented by a character matrix. The programmer sets up each window to look as they want the display to look, and then tells the curses package to update the screen. The library determines a minimal set of changes needed to update the display and then executes these using the terminal's specific capabilities and control sequences.

In short, this means that the programmer simply creates a character matrix of how the screen should look and lets curses handle the work.

The curses API is described in several places.[2] Most implementations of curses use a database that can describe the capabilities of thousands of different terminals. There are a few implementations, such as PDCurses, which use specialized device drivers rather than a terminal database. Most implementations use terminfo; some use termcap. Curses has the advantage of back-portability to character-cell terminals and simplicity. For an application that does not require bit-mapped graphics or multiple fonts, an interface implementation using curses will usually be much simpler and faster than one using an X toolkit.

History

The first curses library was written by Ken Arnold and originally released with BSD UNIX, where it was used for several games, most notably Rogue.[3][4][5] Some improvements were made to the BSD library in the 1990s as "4.4BSD" curses, e.g., to provide more than one type of video highlighting. However, those are not widely used.

The name "curses" is a pun on cursor optimization.[6] Sometimes it is incorrectly stated that curses was used by the vi editor. In fact the code in curses that optimizes moving the cursor from one place on the screen to another was borrowed from vi, which predated curses.[4]

According to Goodheart, Kenneth Arnold's original implementation of curses started by reusing functions from the termcap library, and adding to that.[7] A few years later, Mark Horton, who had made improvements to the vi and termcap sources at Berkeley, went to AT&T Corporation and made a different version using terminfo, which became part of UNIX System III and UNIX System V. Due to licensing restrictions on the latter, the BSD and AT&T versions of the library were developed independently. In addition to the termcap/terminfo improvement, other improvements were made in the AT&T version:

video highlighting (bold, underline)
The BSD version supported only standout.
line-drawing
The BSD version gave little support here.
colors
This was not anticipated in the BSD version.

AT&T curses development appears to have halted in the mid-1990s when X/Open Curses was defined. [8] However, development of ncurses and PDCurses continues. A version of BSD curses continues to be maintained in the NetBSD operating system (wide character support, termcap to terminfo migration, etc.).

pcurses and PDCurses

Main article: PDCurses

Different lines of development started by imitating the AT&T curses, from at least three implementations: pcurses by Pavel Curtis (started in 1982), PDCurses (Public Domain curses) by Mark Hessling to support his editor THE (started in 1987) as well as Rexx/Curses,[9] and PC curses (version 1.4 and earlier by Bjorn Larsson based inspired by Pavel Curtis' library before 1990.)[10][11]

ncurses

Main article: ncurses

ncurses (new curses) "originated as pcurses ... and was re-issued as ncurses 1.8.1 in late 1993".[12] ncurses is the most widely known implementation of curses, and has motivated further development of other variations, such as BSD curses in the NetBSD project. [13] [14]

Portability

Although the ncurses library was initially developed under Linux, OpenBSD, FreeBSD, and NetBSD it has been ported to many other ANSI/POSIX UNIX systems, mainly by Thomas Dickey. PDCurses, while not identical to ncurses, uses the same function calls and operates the same way as ncurses does except that PDCurses targets different devices, e.g., console windows for DOS, Win32, OS/2, as well as X11. Porting between the two is not difficult. For example, the roguelike game ADOM was written for Linux and ncurses, later ported to DOS and PDCurses.[15][16]

Screenshots

Curses-based software

Live Upgrade (lu) command, built upon FMLI which uses Curses

Curses-based software is software whose user interface is implemented through the Curses library, or a compatible library (such as Ncurses).

Curses is designed to facilitate GUI-like functionality on a text-only device, such as a PC running in console mode, a hardware ANSI terminal, a Telnet or SSH client, or similar.

Curses-based programs often have a user interface that resembles a traditional graphical user interface, including 'widgets' such as text boxes and scrollable lists, rather than the command line interface (CLI) most commonly found on text-only devices. This can make them more user-friendly than a CLI-based program, while still being able to run on text-only devices. Curses-based software can also have a lighter resource footprint and operate on a wider range of systems (both in terms of hardware and software) than their GUI-based counterparts. This includes old pre-1990 machines along with modern embedded systems using text-only displays.

However, not all Curses-based software employs a text user interface which resembles a graphical user interface. One counterexample would be the popular vi text editor, which while not being CLI-based, uses memorized keyboard commands almost exclusively, rather than the prompting TUI/GUI style, which relies more on recognition than recall.

Curses is most commonly associated with Unix-like operating systems, although implementations for Microsoft Windows also exist.

See also

References

  1. ↑ Thomas E. Dickey. "NCURSES - Frequently Asked Questions".
  2. ↑ John Strang, Programming with curses, O'Reilly, ISBN 0-937175-02-1
  3. ↑ Peter H. Salus (October 1994). "The history of Unix is as much about collaboration as it is about technology". Byte.
  4. 1 2 Arnold, K. C. R. C. (1977). "Screen Updating and Cursor Movement Optimization: A Library Package.". University of California, Berkeley.
  5. ↑ Kenneth C. R. C. Arnold; Elan Amir (December 1992). "Screen Updating and Cursor Movement Optimization: A Library Package".
  6. ↑ Thomas E. Dickey. "NCURSES - Frequently Asked Questions".
  7. ↑ Goodheart, Berny (1991). UNIX Curses Explained. Prentice Hall. p. xi. ISBN 0-13-931957-3.
  8. ↑ "X/Open Curses, Issue 4 Version 2, Reference Pages". The Open Group. 1997.
  9. ↑ Mark Hessling (2008). "Rexx/Curses". SourceForge project rexxcurses. Retrieved 2014-02-10.
  10. ↑ F. Ellermann (1993-07-26). "CURSES.NEW in pccurses.zip". Retrieved 2014-02-10. based on PC curses (version 1.4) written by Bjorn Larsson
  11. ↑ Bjorn Larsson (1990-01-14). "README.NOW in pccurs14.zip". Retrieved 2014-02-10. PCcurses is a port/rewrite of Pavel Curtis' [package] delete character in |quote= at position 45 (help)
  12. ↑ Thomas E. Dickey (December 1996). "NCURSES - New Curses".
  13. ↑ NetBSD project (February 2004). "CURSES_SCREEN(3), NetBSD Library Functions Manual".
  14. ↑ Ruibiao Qiu (September 2005). "NetBSD-SoC: Wide Character Support in NetBSD curses Library".
  15. ↑ Thomas Biskup (1994–2007). "ADOM - The Past". Retrieved 2007-11-16.
  16. ↑ Thomas Biskup (March 15, 1996). "New Game: ADOM (MS-DOS, MS-Windows, and Linux only)". Newsgroup: rec.games.roguelike.announce. Retrieved 2007-11-16.

External links

This article is issued from Wikipedia - version of the Sunday, April 10, 2016. The text is available under the Creative Commons Attribution/Share Alike but additional terms may apply for the media files.