Newt (programming library): Difference between revisions
m Update latest release version |
m Added short description Tags: Mobile edit Mobile app edit iOS app edit App description add |
||
| Line 1: | Line 1: | ||
{{Short description|Software library for user interfaces}} |
|||
{{Multiple issues| |
{{Multiple issues| |
||
{{refimprove|date=June 2016}} |
{{refimprove|date=June 2016}} |
||
Latest revision as of 09:29, 1 October 2024
 | This article has multiple issues. Please help improve it or discuss these issues on the talk page. (Learn how and when to remove these messages)
|
 Partimage tool that uses Newt to create its user interface | |
| Original author(s) | Erik Troan, Red Hat engineer |
|---|---|
| Developer(s) | Miroslav Lichvar |
| Initial release | 1996 |
| Stable release | 0.52.24
/ October 25, 2023[1] |
| Written in | C |
| Operating system | Linux, Cross-platform (Live CD) |
| Size | about 850 Kb when installed on i686 platform. |
| Type | Widget toolkit |
| License | GNU Lesser General Public License |
| Website | pagure |
Newt is a programming library for color text mode, widget-based user interfaces. Newt can be used to add stacked windows, entry widgets, checkboxes, radio buttons, labels, plain text fields, scrollbars, etc., to text user interfaces. This package also contains the shared library needed by programs built with newt, as well as a CLI application whiptail, which provides the most commonly used features of dialog. Newt is based on the slang library. It abbreviates from Not Erik's Windowing Toolkit.
Overview
[edit]Newt was originally designed for use in the install code of Red Hat Linux and is written mostly focusing on clear interface, simplicity and small footprint.[2] Because of that, unlike most recent GUI engines, it does not use an event-driven architecture.
Windows must be created and destroyed as a stack (the order of discarding is the exact opposite to that of creation). The top level window is always modal. Many behaviours, such as widget traversal order, are difficult or impossible to change.
Mouse control appears to be supported in the source code,[3] using GPM (a mouse-driver) but many users report Newt and Whiptail not responding to mouse control.[4][5]
These restrictions simplify the design of the library as well as the code of programs using it, though they impose limitations on user interface design.
Usage
[edit]The capabilities are fully adequate for the installation process, and Newt was used for the user friendly OS installers. It is also used in some system tools (like Partimage) that focus more on functionality than on looking attractive to the end user.
Interoperability
[edit]Newt is written in C. However, there are bindings to other languages like Python.
Variants
[edit]gNewt project (no longer active) provides an alternative implementation that uses GTK instead of the text based interface. It is fully compatible with the official Newt implementation and can be replaced at run time, without recompilation. Like any other GTK components, gNewt controls can also use mouse input whereas the original Newt only supports the keyboard.
See also
[edit]
- nparted - Newt text interface for GNU Parted
- ncurses - the text interface library for which dialog was written in 1994
References
[edit]- ^ https://pagure.io/newt/releases - accessed on 2023/12/14
- ^ "Newt tutorial". Archived from the original on 2017-01-24. Retrieved 2011-07-03.
- ^ "Official page of Newt and Whiptail, including git source code repository".
- ^ "Stack Exchange question about using mouse in whiptail".
- ^ "Debian mailing list question about dialog package with mouse support".
External links
[edit]- Official website
- Wikibooks' Bash Shell Scripting/Whiptail tutorial
