Newt (programming library)
- 1 min read
- 4 chapters
Related on Lably
Through Library (computing), User interface and Python (programming language)
Overview
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. 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, using GPM (a mouse-driver) but many users report Newt and Whiptail not responding to mouse control.
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.
Sign in to keep reading
3 more chapters are free with a Lably account.
Usage
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
Newt is written in C. However, there are bindings to other languages like Python.
Variants
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.