Convert Figma logo to code with AI

chjj logoblessed

A high-level terminal interface library for node.js.

11,248
531
11,248
257

Top Related Projects

26,391

🌈 React for interactive command-line apps

Build terminal dashboards using ascii/ansi art and javascript

13,182

Golang terminal dashboard

9,886

Minimalist Go package aimed at creating Console User Interfaces.

10,905

Terminal UI library with rich, interactive widgets — written in Golang

10,830

Build terminal user interfaces and dashboards using Rust

Quick Overview

Blessed is a high-level terminal interface library for Node.js. It provides a powerful and feature-rich API for creating complex, interactive terminal applications with ease. Blessed offers a wide range of widgets and tools for building sophisticated command-line interfaces (CLIs) and text-based user interfaces (TUIs).

Pros

  • Rich set of pre-built widgets and layouts for rapid development
  • Highly customizable with extensive styling options
  • Cross-platform compatibility (works on Windows, macOS, and Linux)
  • Active community and ongoing development

Cons

  • Steep learning curve for beginners
  • Documentation can be overwhelming due to the extensive API
  • Performance may degrade with complex layouts or large amounts of content
  • Some users report occasional rendering issues on certain terminals

Code Examples

  1. Creating a simple box:
const blessed = require('blessed');

const screen = blessed.screen();
const box = blessed.box({
  top: 'center',
  left: 'center',
  width: '50%',
  height: '50%',
  content: 'Hello, Blessed!',
  border: {
    type: 'line'
  },
  style: {
    border: {
      fg: '#f0f0f0'
    }
  }
});

screen.append(box);
screen.render();
  1. Adding a list to the screen:
const list = blessed.list({
  top: 'center',
  left: 'center',
  width: '50%',
  height: '50%',
  items: ['Item 1', 'Item 2', 'Item 3'],
  border: {
    type: 'line'
  },
  style: {
    selected: {
      bg: 'blue'
    }
  }
});

screen.append(list);
list.focus();
screen.render();
  1. Creating a form with input:
const form = blessed.form({
  parent: screen,
  width: '50%',
  left: 'center',
  keys: true,
  vi: true
});

const input = blessed.textbox({
  parent: form,
  top: 0,
  left: 0,
  height: 3,
  inputOnFocus: true,
  border: {
    type: 'line'
  },
  name: 'username'
});

const submit = blessed.button({
  parent: form,
  top: 3,
  left: 0,
  content: 'Submit',
  shrink: true,
  mouse: true,
  keys: true
});

submit.on('press', () => {
  form.submit();
});

form.on('submit', (data) => {
  console.log('Form submitted:', data);
  process.exit(0);
});

input.focus();
screen.render();

Getting Started

To get started with Blessed, follow these steps:

  1. Install Blessed in your Node.js project:

    npm install blessed
    
  2. Create a new JavaScript file (e.g., app.js) and add the following code:

    const blessed = require('blessed');
    
    const screen = blessed.screen({
      smartCSR: true
    });
    
    screen.title = 'My Blessed App';
    
    const box = blessed.box({
      top: 'center',
      left: 'center',
      width: '50%',
      height: '50%',
      content: 'Welcome to Blessed!',
      border: {
        type: 'line'
      },
      style: {
        border: {
          fg: 'white'
        }
      }
    });
    
    screen.append(box);
    
    screen.key(['escape', 'q', 'C-c'], function(ch, key) {
      return process.exit(0);
    });
    
    screen.render();
    
  3. Run the application:

    node app.js
    

This will create a simple Blessed application with a centered box displaying a welcome message. Press 'q', 'Esc

Competitor Comparisons

26,391

🌈 React for interactive command-line apps

Pros of Ink

  • Built on React, allowing developers to leverage familiar component-based architecture
  • Offers a more modern and declarative approach to building CLI interfaces
  • Provides better TypeScript support out of the box

Cons of Ink

  • Smaller community and ecosystem compared to Blessed
  • Higher learning curve for developers not familiar with React
  • May have performance overhead due to React's virtual DOM

Code Comparison

Blessed example:

const blessed = require('blessed');
const screen = blessed.screen();
const box = blessed.box({
  content: 'Hello, world!'
});
screen.append(box);

Ink example:

import React from 'react';
import {render, Text} from 'ink';

const App = () => <Text>Hello, world!</Text>;
render(<App />);

Summary

Ink offers a modern, React-based approach to building CLI interfaces, which can be advantageous for developers already familiar with React. It provides better TypeScript support and a declarative programming style. However, Blessed has a larger community and ecosystem, potentially lower performance overhead, and may be easier to learn for developers without React experience. The choice between the two depends on the specific project requirements and the development team's expertise.

Build terminal dashboards using ascii/ansi art and javascript

Pros of blessed-contrib

  • Provides a rich set of pre-built widgets and charts for terminal dashboards
  • Offers more advanced visualization capabilities out-of-the-box
  • Simplifies the creation of complex terminal UIs with minimal code

Cons of blessed-contrib

  • Higher learning curve due to more complex API and widget system
  • Less flexibility for custom low-level terminal manipulations
  • Larger package size and potentially higher resource usage

Code Comparison

blessed:

const blessed = require('blessed');
const screen = blessed.screen();
const box = blessed.box({
  content: 'Hello, world!'
});
screen.append(box);
screen.render();

blessed-contrib:

const blessed = require('blessed');
const contrib = require('blessed-contrib');
const screen = blessed.screen();
const grid = new contrib.grid({rows: 1, cols: 1});
const line = grid.set(0, 0, 1, 1, contrib.line, {
  style: { line: "yellow", text: "green", baseline: "black" },
  xLabelPadding: 3,
  xPadding: 5,
  label: 'Stocks'
});
screen.render();

The code comparison illustrates that blessed-contrib requires more setup but provides more advanced widgets like charts, while blessed offers a simpler API for basic terminal UI elements.

13,182

Golang terminal dashboard

Pros of termui

  • Written in Go, offering better performance and easier deployment
  • More modern and actively maintained, with recent updates
  • Focuses on data visualization with built-in widgets for charts and graphs

Cons of termui

  • Less extensive widget library compared to blessed
  • Steeper learning curve for developers not familiar with Go
  • Limited cross-platform support (primarily targets Unix-like systems)

Code Comparison

termui example:

ui.Init()
defer ui.Close()

p := widgets.NewParagraph()
p.Text = "Hello World!"
p.SetRect(0, 0, 25, 5)

ui.Render(p)

blessed example:

const blessed = require('blessed');
const screen = blessed.screen();

const box = blessed.box({
  content: 'Hello World!'
});

screen.append(box);
screen.render();

Both examples demonstrate creating a simple text display, but termui's approach is more strongly typed and structured, while blessed offers a more flexible, JavaScript-style API.

9,886

Minimalist Go package aimed at creating Console User Interfaces.

Pros of gocui

  • Written in Go, offering better performance and concurrency support
  • Lightweight and minimalistic, with a smaller codebase
  • Provides a simpler API, making it easier to learn and use for basic TUI applications

Cons of gocui

  • Less feature-rich compared to blessed, with fewer built-in widgets and layout options
  • Smaller community and ecosystem, resulting in fewer examples and third-party extensions
  • Limited cross-platform support, primarily focused on Unix-like systems

Code Comparison

blessed example:

const blessed = require('blessed');
const screen = blessed.screen();
const box = blessed.box({
  content: 'Hello, world!'
});
screen.append(box);

gocui example:

g, err := gocui.NewGui(gocui.OutputNormal)
if err != nil {
    // handle error
}
defer g.Close()
g.SetManagerFunc(layout)

Both libraries provide ways to create and manage terminal user interfaces, but blessed offers a more extensive set of features and widgets out of the box. gocui, on the other hand, provides a simpler and more performant approach for Go developers, albeit with fewer built-in components.

10,905

Terminal UI library with rich, interactive widgets — written in Golang

Pros of tview

  • Written in Go, offering better performance and concurrency support
  • More modern and actively maintained, with regular updates and improvements
  • Simpler API and easier to get started with for new users

Cons of tview

  • Less feature-rich compared to blessed's extensive widget set
  • Smaller community and ecosystem, with fewer third-party extensions
  • Limited to Go language, while blessed can be used in Node.js projects

Code Comparison

tview:

app := tview.NewApplication()
box := tview.NewBox().SetBorder(true).SetTitle("Hello, world!")
if err := app.SetRoot(box, true).Run(); err != nil {
    panic(err)
}

blessed:

const blessed = require('blessed');
const screen = blessed.screen();
const box = blessed.box({
  border: { type: 'line' },
  content: 'Hello, world!'
});
screen.append(box);
screen.render();

Both examples create a simple bordered box with text, demonstrating the basic setup and rendering process for each library. tview's code is more concise and type-safe due to Go's nature, while blessed offers more flexibility in configuration options.

10,830

Build terminal user interfaces and dashboards using Rust

Pros of tui-rs

  • Written in Rust, offering memory safety and performance benefits
  • More modern and actively maintained
  • Supports custom widgets and flexible layouts

Cons of tui-rs

  • Smaller ecosystem and community compared to Blessed
  • Steeper learning curve for developers not familiar with Rust
  • Less comprehensive documentation and examples

Code Comparison

tui-rs:

use tui::widgets::{Block, Borders};
let block = Block::default()
    .title("Block")
    .borders(Borders::ALL);
f.render_widget(block, chunks[0]);

Blessed:

const blessed = require('blessed');
const box = blessed.box({
  top: 'center',
  left: 'center',
  width: '50%',
  height: '50%',
  border: {
    type: 'line'
  },
  content: 'Hello World!'
});

Summary

tui-rs is a modern TUI library written in Rust, offering performance and safety benefits. It provides flexibility in creating custom widgets and layouts. However, it has a smaller ecosystem and steeper learning curve compared to Blessed.

Blessed, being a more established JavaScript library, has a larger community and more extensive documentation. It's easier to get started with for JavaScript developers but may lack some of the performance advantages of tui-rs.

The choice between the two depends on the developer's familiarity with the respective languages, project requirements, and preference for ecosystem size versus modern language features.

Convert Figma logo designs to code with AI

Visual Copilot

Introducing Visual Copilot: A new AI model to turn Figma designs to high quality code using your components.

Try Visual Copilot

README

blessed

A curses-like library with a high level terminal interface API for node.js.

blessed

Blessed is over 16,000 lines of code and terminal goodness. It's completely implemented in javascript, and its goal consists of two things:

  1. Reimplement ncurses entirely by parsing and compiling terminfo and termcap, and exposing a Program object which can output escape sequences compatible with any terminal.

  2. Implement a widget API which is heavily optimized for terminals.

The blessed renderer makes use of CSR (change-scroll-region), and BCE (back-color-erase). It draws the screen using the painter's algorithm and is sped up with smart cursor movements and a screen damage buffer. This means rendering of your application will be extremely efficient: blessed only draws the changes (damage) to the screen.

Blessed is arguably as accurate as ncurses, but even more optimized in some ways. The widget library gives you an API which is reminiscent of the DOM. Anyone is able to make an awesome terminal application with blessed. There are terminal widget libraries for other platforms (primarily python and perl), but blessed is possibly the most DOM-like (dare I say the most user-friendly?).

Blessed has been used to implement other popular libraries and programs. Examples include: the slap text editor and blessed-contrib. The blessed API itself has gone on to inspire termui for Go.

Install

$ npm install blessed

Example

This will render a box with line borders containing the text 'Hello world!', perfectly centered horizontally and vertically.

NOTE: It is recommend you use either smartCSR or fastCSR as a blessed.screen option. This will enable CSR when scrolling text in elements or when manipulating lines.

var blessed = require('blessed');

// Create a screen object.
var screen = blessed.screen({
  smartCSR: true
});

screen.title = 'my window title';

// Create a box perfectly centered horizontally and vertically.
var box = blessed.box({
  top: 'center',
  left: 'center',
  width: '50%',
  height: '50%',
  content: 'Hello {bold}world{/bold}!',
  tags: true,
  border: {
    type: 'line'
  },
  style: {
    fg: 'white',
    bg: 'magenta',
    border: {
      fg: '#f0f0f0'
    },
    hover: {
      bg: 'green'
    }
  }
});

// Append our box to the screen.
screen.append(box);

// Add a png icon to the box
var icon = blessed.image({
  parent: box,
  top: 0,
  left: 0,
  type: 'overlay',
  width: 'shrink',
  height: 'shrink',
  file: __dirname + '/my-program-icon.png',
  search: false
});

// If our box is clicked, change the content.
box.on('click', function(data) {
  box.setContent('{center}Some different {red-fg}content{/red-fg}.{/center}');
  screen.render();
});

// If box is focused, handle `enter`/`return` and give us some more content.
box.key('enter', function(ch, key) {
  box.setContent('{right}Even different {black-fg}content{/black-fg}.{/right}\n');
  box.setLine(1, 'bar');
  box.insertLine(1, 'foo');
  screen.render();
});

// Quit on Escape, q, or Control-C.
screen.key(['escape', 'q', 'C-c'], function(ch, key) {
  return process.exit(0);
});

// Focus our element.
box.focus();

// Render the screen.
screen.render();

Documentation

Widgets

Other

Mechanics

Notes

Widgets

Blessed comes with a number of high-level widgets so you can avoid all the nasty low-level terminal stuff.

Base Nodes

Node (from EventEmitter)

The base node which everything inherits from.

Options:
  • screen - The screen to be associated with.
  • parent - The desired parent.
  • children - An arrray of children.
Properties:
  • Inherits all from EventEmitter.
  • type - Type of the node (e.g. box).
  • options - Original options object.
  • parent - Parent node.
  • screen - Parent screen.
  • children - Array of node's children.
  • _data, , $ - An object for any miscellanous user data.
  • index - Render index (document order index) of the last render call.
Events:
  • Inherits all from EventEmitter.
  • adopt - Received when node is added to a parent.
  • remove - Received when node is removed from it's current parent.
  • reparent - Received when node gains a new parent.
  • attach - Received when node is attached to the screen directly or somewhere in its ancestry.
  • detach - Received when node is detached from the screen directly or somewhere in its ancestry.
Methods:
  • Inherits all from EventEmitter.
  • prepend(node) - Prepend a node to this node's children.
  • append(node) - Append a node to this node's children.
  • remove(node) - Remove child node from node.
  • insert(node, i) - Insert a node to this node's children at index i.
  • insertBefore(node, refNode) - Insert a node to this node's children before the reference node.
  • insertAfter(node, refNode) - Insert a node from node after the reference node.
  • detach() - Remove node from its parent.
  • emitDescendants(type, args..., [iterator]) - Emit event for element, and recursively emit same event for all descendants.
  • get(name, [default]) - Get user property with a potential default value.
  • set(name, value) - Set user property to value.

Screen (from Node)

The screen on which every other node renders.

Options:
  • program - The blessed Program to be associated with. Will be automatically instantiated if none is provided.
  • smartCSR - Attempt to perform CSR optimization on all possible elements (not just full-width ones, elements with uniform cells to their sides). This is known to cause flickering with elements that are not full-width, however, it is more optimal for terminal rendering.
  • fastCSR - Do CSR on any element within 20 cols of the screen edge on either side. Faster than smartCSR, but may cause flickering depending on what is on each side of the element.
  • useBCE - Attempt to perform back_color_erase optimizations for terminals that support it. It will also work with terminals that don't support it, but only on lines with the default background color. As it stands with the current implementation, it's uncertain how much terminal performance this adds at the cost of overhead within node.
  • resizeTimeout - Amount of time (in ms) to redraw the screen after the terminal is resized (Default: 300).
  • tabSize - The width of tabs within an element's content.
  • autoPadding - Automatically position child elements with border and padding in mind (NOTE: this is a recommended option. It may become default in the future).
  • cursor.artificial - Have blessed draw a custom cursor and hide the terminal cursor (experimental).
  • cursor.shape - Shape of the cursor. Can be: block, underline, or line.
  • cursor.blink - Whether the cursor blinks.
  • cursor.color - Color of the color. Accepts any valid color value (null is default).
  • log - Create a log file. See log method.
  • dump - Dump all output and input to desired file. Can be used together with log option if set as a boolean.
  • debug - Debug mode. Enables usage of the debug method. Also creates a debug console which will display when pressing F12. It will display all log and debug messages.
  • ignoreLocked - Array of keys in their full format (e.g. C-c) to ignore when keys are locked or grabbed. Useful for creating a key that will always exit no matter whether the keys are locked.
  • dockBorders - Automatically "dock" borders with other elements instead of overlapping, depending on position (experimental). For example: These border-overlapped elements:
┌─────────┌─────────┐
│ box1    │ box2    │
└─────────└─────────┘

Become:

┌─────────┬─────────┐
│ box1    │ box2    │
└─────────┴─────────┘
  • ignoreDockContrast - Normally, dockable borders will not dock if the colors or attributes are different. This option will allow them to dock regardless. It may produce some odd looking multi-colored borders though.
  • fullUnicode - Allow for rendering of East Asian double-width characters, utf-16 surrogate pairs, and unicode combining characters. This allows you to display text above the basic multilingual plane. This is behind an option because it may affect performance slightly negatively. Without this option enabled, all double-width, surrogate pair, and combining characters will be replaced by '??', '?', '' respectively. (NOTE: iTerm2 cannot display combining characters properly. Blessed simply removes them from an element's content if iTerm2 is detected).
  • sendFocus - Send focus events after mouse is enabled.
  • warnings - Display warnings (such as the output not being a TTY, similar to ncurses).
  • forceUnicode - Force blessed to use unicode even if it is not detected via terminfo, env variables, or windows code page. If value is true unicode is forced. If value is false non-unicode is forced (default: null).
  • input/output - Input and output streams. process.stdin/process.stdout by default, however, it could be a net.Socket if you want to make a program that runs over telnet or something of that nature.
  • terminal - TERM name used for terminfo parsing. The $TERM env variable is used by default.
  • title - Set the terminal window title if possible.
Properties:
  • Inherits all from Node.
  • program - The blessed Program object.
  • tput - The blessed Tput object (only available if you passed tput: true to the Program constructor.)
  • focused - Top of the focus history stack.
  • width - Width of the screen (same as program.cols).
  • height - Height of the screen (same as program.rows).
  • cols - Same as screen.width.
  • rows - Same as screen.height.
  • left - Relative left offset, always zero.
  • right - Relative right offset, always zero.
  • top - Relative top offset, always zero.
  • bottom - Relative bottom offset, always zero.
  • aleft - Absolute left offset, always zero.
  • aright - Absolute right offset, always zero.
  • atop - Absolute top offset, always zero.
  • abottom - Absolute bottom offset, always zero.
  • grabKeys - Whether the focused element grabs all keypresses.
  • lockKeys - Prevent keypresses from being received by any element.
  • hover - The currently hovered element. Only set if mouse events are bound.
  • terminal - Set or get terminal name. Set calls screen.setTerminal() internally.
  • title - Set or get window title.
Events:
  • Inherits all from Node.
  • resize - Received on screen resize.
  • mouse - Received on mouse events.
  • keypress - Received on key events.
  • element [name] - Global events received for all elements.
  • key [name] - Received on key event for [name].
  • focus, blur - Received when the terminal window focuses/blurs. Requires a terminal supporting the focus protocol and focus needs to be passed to program.enableMouse().
  • prerender - Received before render.
  • render - Received on render.
  • warning - Received when blessed notices something untoward (output is not a tty, terminfo not found, etc).
  • destroy - Received when the screen is destroyed (only useful when using multiple screens).
Methods:
  • Inherits all from Node.
  • log(msg, ...) - Write string to the log file if one was created.
  • debug(msg, ...) - Same as the log method, but only gets called if the debug option was set.
  • alloc() - Allocate a new pending screen buffer and a new output screen buffer.
  • realloc() - Reallocate the screen buffers and clear the screen.
  • draw(start, end) - Draw the screen based on the contents of the screen buffer.
  • render() - Render all child elements, writing all data to the screen buffer and drawing the screen.
  • clearRegion(x1, x2, y1, y2) - Clear any region on the screen.
  • fillRegion(attr, ch, x1, x2, y1, y2) - Fill any region with a character of a certain attribute.
  • focusOffset(offset) - Focus element by offset of focusable elements.
  • focusPrevious() - Focus previous element in the index.
  • focusNext() - Focus next element in the index.
  • focusPush(element) - Push element on the focus stack (equivalent to screen.focused = el).
  • focusPop() - Pop element off the focus stack.
  • saveFocus() - Save the focused element.
  • restoreFocus() - Restore the saved focused element.
  • rewindFocus() - "Rewind" focus to the last visible and attached element.
  • key(name, listener) - Bind a keypress listener for a specific key.
  • onceKey(name, listener) - Bind a keypress listener for a specific key once.
  • unkey(name, listener) - Remove a keypress listener for a specific key.
  • spawn(file, args, options) - Spawn a process in the foreground, return to blessed app after exit.
  • exec(file, args, options, callback) - Spawn a process in the foreground, return to blessed app after exit. Executes callback on error or exit.
  • readEditor([options], callback) - Read data from text editor.
  • setEffects(el, fel, over, out, effects, temp) - Set effects based on two events and attributes.
  • insertLine(n, y, top, bottom) - Insert a line into the screen (using csr: this bypasses the output buffer).
  • deleteLine(n, y, top, bottom) - Delete a line from the screen (using csr: this bypasses the output buffer).
  • insertBottom(top, bottom) - Insert a line at the bottom of the screen.
  • insertTop(top, bottom) - Insert a line at the top of the screen.
  • deleteBottom(top, bottom) - Delete a line at the bottom of the screen.
  • deleteTop(top, bottom) - Delete a line at the top of the screen.
  • enableMouse([el]) - Enable mouse events for the screen and optionally an element (automatically called when a form of on('mouse') is bound).
  • enableKeys([el]) - Enable keypress events for the screen and optionally an element (automatically called when a form of on('keypress') is bound).
  • enableInput([el]) - Enable key and mouse events. Calls bot enableMouse and enableKeys.
  • copyToClipboard(text) - Attempt to copy text to clipboard using iTerm2's proprietary sequence. Returns true if successful.
  • cursorShape(shape, blink) - Attempt to change cursor shape. Will not work in all terminals (see artificial cursors for a solution to this). Returns true if successful.
  • cursorColor(color) - Attempt to change cursor color. Returns true if successful.
  • cursorReset() - Attempt to reset cursor. Returns true if successful.
  • screenshot([xi, xl, yi, yl]) - Take an SGR screenshot of the screen within the region. Returns a string containing only characters and SGR codes. Can be displayed by simply echoing it in a terminal.
  • destroy() - Destroy the screen object and remove it from the global list. Also remove all global events relevant to the screen object. If all screen objects are destroyed, the node process is essentially reset to its initial state.
  • setTerminal(term) - Reset the terminal to term. Reloads terminfo.

Element (from Node)

The base element.

Options:
  • fg, bg, bold, underline - Attributes.
  • style - May contain attributes in the format of:
  {
    fg: 'blue',
    bg: 'black',
    border: {
      fg: 'blue'
    },
    scrollbar: {
      bg: 'blue'
    },
    focus: {
      bg: 'red'
    },
    hover: {
      bg: 'red'
    }
  }
  • border - Border object, see below.
  • content - Element's text content.
  • clickable - Element is clickable.
  • input, keyable - Element is focusable and can receive key input.
  • focused - Element is focused.
  • hidden - Whether the element is hidden.
  • label - A simple text label for the element.
  • hoverText - A floating text label for the element which appears on mouseover.
  • align - Text alignment: left, center, or right.
  • valign - Vertical text alignment: top, middle, or bottom.
  • shrink - Shrink/flex/grow to content and child elements. Width/height during render.
  • padding - Amount of padding on the inside of the element. Can be a number or an object containing the properties: left, right, top, and bottom.
  • width, height - Width/height of the element, can be a number, percentage (0-100%), or keyword (half or shrink). Percentages can also have offsets (50%+1, 50%-1).
  • left, right, top, bottom - Offsets of the element relative to its parent. Can be a number, percentage (0-100%), or keyword (center). right and bottom do not accept keywords. Percentages can also have offsets (50%+1, 50%-1).
  • position - Can contain the above options.
  • scrollable - Whether the element is scrollable or not.
  • ch - Background character (default is whitespace ).
  • draggable - Allow the element to be dragged with the mouse.
  • shadow - Draw a translucent offset shadow behind the element.
Properties:
  • Inherits all from Node.
  • name - Name of the element. Useful for form submission.
  • border - Border object.
    • type - Type of border (line or bg). bg by default.
    • ch - Character to use if bg type, default is space.
    • bg, fg - Border foreground and background, must be numbers (-1 for default).
    • bold, underline - Border attributes.
  • style - Contains attributes (e.g. fg/bg/underline). See above.
  • position - Raw width, height, and offsets.
  • content - Raw text content.
  • hidden - Whether the element is hidden or not.
  • visible - Whether the element is visible or not.
  • detached - Whether the element is attached to a screen in its ancestry somewhere.
  • fg, bg - Foreground and background, must be numbers (-1 for default).
  • bold, underline - Attributes.
  • width - Calculated width.
  • height - Calculated height.
  • left - Calculated relative left offset.
  • right - Calculated relative right offset.
  • top - Calculated relative top offset.
  • bottom - Calculated relative bottom offset.
  • aleft - Calculated absolute left offset.
  • aright - Calculated absolute right offset.
  • atop - Calculated absolute top offset.
  • abottom - Calculated absolute bottom offset.
  • draggable - Whether the element is draggable. Set to true to allow dragging.
Events:
  • Inherits all from Node.
  • blur, focus - Received when an element is focused or unfocused.
  • mouse - Received on mouse events for this element.
    • mousedown, mouseup - Mouse button was pressed or released.
    • wheeldown, wheelup - Wheel was scrolled down or up.
    • mouseover, mouseout - Element was hovered or unhovered.
    • mousemove - Mouse was moved somewhere on this element.
    • click - Element was clicked (slightly smarter than mouseup).
  • keypress - Received on key events for this element.
  • move - Received when the element is moved.
  • resize - Received when the element is resized.
  • key [name] - Received on key event for [name].
  • prerender - Received before a call to render.
  • render - Received after a call to render.
  • hide - Received when element becomes hidden.
  • show - Received when element is shown.
  • destroy - Received when element is destroyed.
Methods:
  • Inherits all from Node.
  • Note: If the scrollable option is enabled, Element inherits all methods from ScrollableBox.
  • render() - Write content and children to the screen buffer.
  • hide() - Hide element.
  • show() - Show element.
  • toggle() - Toggle hidden/shown.
  • focus() - Focus element.
  • key(name, listener) - Bind a keypress listener for a specific key.
  • onceKey(name, listener) - Bind a keypress listener for a specific key once.
  • unkey(name, listener) - Remove a keypress listener for a specific key.
  • onScreenEvent(type, handler) - Same asel.on('screen', ...) except this will automatically keep track of which listeners are bound to the screen object. For use with removeScreenEvent(), free(), and destroy().
  • removeScreenEvent(type, handler) - Same asel.removeListener('screen', ...) except this will automatically keep track of which listeners are bound to the screen object. For use with onScreenEvent(), free(), and destroy().
  • free() - Free up the element. Automatically unbind all events that may have been bound to the screen object. This prevents memory leaks. For use with onScreenEvent(), removeScreenEvent(), and destroy().
  • destroy() - Same as the detach() method, except this will automatically call free() and unbind any screen events to prevent memory leaks. for use with onScreenEvent(), removeScreenEvent(), and free().
  • setIndex(z) - Set the z-index of the element (changes rendering order).
  • setFront() - Put the element in front of its siblings.
  • setBack() - Put the element in back of its siblings.
  • setLabel(text/options) - Set the label text for the top-left corner. Example options: {text:'foo',side:'left'}
  • removeLabel() - Remove the label completely.
  • setHover(text/options) - Set a hover text box to follow the cursor. Similar to the "title" DOM attribute in the browser. Example options: {text:'foo'}
  • removeHover() - Remove the hover label completely.
  • enableMouse() - Enable mouse events for the element (automatically called when a form of on('mouse') is bound).
  • enableKeys() - Enable keypress events for the element (automatically called when a form of on('keypress') is bound).
  • enableInput() - Enable key and mouse events. Calls bot enableMouse and enableKeys.
  • enableDrag() - Enable dragging of the element.
  • disableDrag() - Disable dragging of the element.
  • screenshot([xi, xl, yi, yl]) - Take an SGR screenshot of the element within the region. Returns a string containing only characters and SGR codes. Can be displayed by simply echoing it in a terminal.
Content Methods

Methods for dealing with text content, line by line. Useful for writing a text editor, irc client, etc.

Note: All of these methods deal with pre-aligned, pre-wrapped text. If you use deleteTop() on a box with a wrapped line at the top, it may remove 3-4 "real" lines (rows) depending on how long the original line was.

The lines parameter can be a string or an array of strings. The line parameter must be a string.

  • setContent(text) - Set the content. Note: When text is input, it will be stripped of all non-SGR escape codes, tabs will be replaced with 8 spaces, and tags will be replaced with SGR codes (if enabled).
  • getContent() - Return content, slightly different from el.content. Assume the above formatting.
  • setText(text) - Similar to setContent, but ignore tags and remove escape codes.
  • getText() - Similar to getContent, but return content with tags and escape codes removed.
  • insertLine(i, lines) - Insert a line into the box's content.
  • deleteLine(i) - Delete a line from the box's content.
  • getLine(i) - Get a line from the box's content.
  • getBaseLine(i) - Get a line from the box's content from the visible top.
  • setLine(i, line) - Set a line in the box's content.
  • setBaseLine(i, line) - Set a line in the box's content from the visible top.
  • clearLine(i) - Clear a line from the box's content.
  • clearBaseLine(i) - Clear a line from the box's content from the visible top.
  • insertTop(lines) - Insert a line at the top of the box.
  • insertBottom(lines) - Insert a line at the bottom of the box.
  • deleteTop() - Delete a line at the top of the box.
  • deleteBottom() - Delete a line at the bottom of the box.
  • unshiftLine(lines) - Unshift a line onto the top of the content.
  • shiftLine(i) - Shift a line off the top of the content.
  • pushLine(lines) - Push a line onto the bottom of the content.
  • popLine(i) - Pop a line off the bottom of the content.
  • getLines() - An array containing the content lines.
  • getScreenLines() - An array containing the lines as they are displayed on the screen.
  • strWidth(text) - Get a string's displayed width, taking into account double-width, surrogate pairs, combining characters, tags, and SGR escape codes.

Boxes

Box (from Element)

A box element which draws a simple box containing content or other elements.

Options:
  • Inherits all from Element.
Properties:
  • Inherits all from Element.
Events:
  • Inherits all from Element.
Methods:
  • Inherits all from Element.

Text (from Element)

An element similar to Box, but geared towards rendering simple text elements.

Options:
  • Inherits all from Element.
  • fill - Fill the entire line with chosen bg until parent bg ends, even if there is not enough text to fill the entire width. (deprecated)
  • align - Text alignment: left, center, or right.

Inherits all options, properties, events, and methods from Element.

Line (from Box)

A simple line which can be line or bg styled.

Options:
  • Inherits all from Box.
  • orientation - Can be vertical or horizontal.
  • type, bg, fg, ch - Treated the same as a border object. (attributes can be contained in style).

Inherits all options, properties, events, and methods from Box.

ScrollableBox (from Box)

DEPRECATED - Use Box with the scrollable option instead.

A box with scrollable content.

Options:
  • Inherits all from Box.
  • baseLimit - A limit to the childBase. Default is Infinity.
  • alwaysScroll - A option which causes the ignoring of childOffset. This in turn causes the childBase to change every time the element is scrolled.
  • scrollbar - Object enabling a scrollbar.
  • scrollbar.style - Style of the scrollbar.
  • scrollbar.track - Style of the scrollbar track if present (takes regular style options).
Properties:
  • Inherits all from Box.
  • childBase - The offset of the top of the scroll content.
  • childOffset - The offset of the chosen item/line.
Events:
  • Inherits all from Box.
  • scroll - Received when the element is scrolled.
Methods:
  • scroll(offset) - Scroll the content by a relative offset.
  • scrollTo(index) - Scroll the content to an absolute index.
  • setScroll(index) - Same as scrollTo.
  • setScrollPerc(perc) - Set the current scroll index in percentage (0-100).
  • getScroll() - Get the current scroll index in lines.
  • getScrollHeight() - Get the actual height of the scrolling area.
  • getScrollPerc() - Get the current scroll index in percentage.
  • resetScroll() - Reset the scroll index to its initial state.

ScrollableText (from ScrollableBox)

DEPRECATED - Use Box with the scrollable and alwaysScroll options instead.

A scrollable text box which can display and scroll text, as well as handle pre-existing newlines and escape codes.

Options:
  • Inherits all from ScrollableBox.
  • mouse - Whether to enable automatic mouse support for this element.
  • keys - Use predefined keys for navigating the text.
  • vi - Use vi keys with the keys option.
Properties:
  • Inherits all from ScrollableBox.
Events:
  • Inherits all from ScrollableBox.
Methods:
  • Inherits all from ScrollableBox.

BigText (from Box)

A box which can render content drawn as 8x14 cell characters using the terminus font.

Options:
  • Inherits all from Box.
  • font - bdf->json font file to use (see ttystudio for instructions on compiling BDFs to JSON).
  • fontBold - bdf->json bold font file to use (see ttystudio for instructions on compiling BDFs to JSON).
  • fch - foreground character. (default: ' ')
Properties:
  • Inherits all from Box.
Events:
  • Inherits all from Box.
Methods:
  • Inherits all from Box.

Lists

List (from Box)

A scrollable list which can display selectable items.

Options:
  • Inherits all from Box.
  • style.selected - Style for a selected item.
  • style.item - Style for an unselected item.
  • mouse - Whether to automatically enable mouse support for this list (allows clicking items).
  • keys - Use predefined keys for navigating the list.
  • vi - Use vi keys with the keys option.
  • items - An array of strings which become the list's items.
  • search - A function that is called when vi mode is enabled and the key / is pressed. This function accepts a callback function which should be called with the search string. The search string is then used to jump to an item that is found in items.
  • interactive - Whether the list is interactive and can have items selected (Default: true).
  • invertSelected - Whether to automatically override tags and invert fg of item when selected (Default: true).
Properties:
  • Inherits all from Box.
Events:
  • Inherits all from Box.
  • select - Received when an item is selected.
  • cancel - List was canceled (when esc is pressed with the keys option).
  • action - Either a select or a cancel event was received.
Methods:
  • Inherits all from Box.
  • add/addItem(text) - Add an item based on a string.
  • removeItem(child) - Removes an item from the list. Child can be an element, index, or string.
  • pushItem(child) - Push an item onto the list.
  • popItem() - Pop an item off the list.
  • unshiftItem(child) - Unshift an item onto the list.
  • shiftItem() - Shift an item off the list.
  • insertItem(i, child) - Inserts an item to the list. Child can be an element, index, or string.
  • getItem(child) - Returns the item element. Child can be an element, index, or string.
  • setItem(child, content) - Set item to content.
  • spliceItem(i, n, item1, ...) - Remove and insert items to the list.
  • clearItems() - Clears all items from the list.
  • setItems(items) - Sets the list items to multiple strings.
  • getItemIndex(child) - Returns the item index from the list. Child can be an element, index, or string.
  • select(index) - Select an index of an item.
  • move(offset) - Select item based on current offset.
  • up(amount) - Select item above selected.
  • down(amount) - Select item below selected.
  • pick(callback) - Show/focus list and pick an item. The callback is executed with the result.
  • fuzzyFind([string/regex/callback]) - Find an item based on its text content.

FileManager (from List)

A very simple file manager for selecting files.

Options:
  • Inherits all from List.
  • cwd - Current working directory.
Properties:
  • Inherits all from List.
  • cwd - Current working directory.
Events:
  • Inherits all from List.
  • cd - Directory was selected and navigated to.
  • file - File was selected.
Methods:
  • Inherits all from List.
  • refresh([cwd], [callback]) - Refresh the file list (perform a readdir on cwd and update the list items).
  • pick([cwd], callback) - Pick a single file and return the path in the callback.
  • reset([cwd], [callback]) - Reset back to original cwd.

ListTable (from List)

A stylized table of text elements with a list.

Options:
  • Inherits all from List.
  • rows/data - Array of array of strings representing rows.
  • pad - Spaces to attempt to pad on the sides of each cell. 2 by default: one space on each side (only useful if the width is shrunken).
  • noCellBorders - Do not draw inner cells.
  • style.header - Header style.
  • style.cell - Cell style.
Properties:
  • Inherits all from List.
Events:
  • Inherits all from List.
Methods:
  • Inherits all from List.
  • setRows/setData(rows) - Set rows in table. Array of arrays of strings.
  table.setData([
    [ 'Animals',  'Foods'  ],
    [ 'Elephant', 'Apple'  ],
    [ 'Bird',     'Orange' ]
  ]);

Listbar (from Box)

A horizontal list. Useful for a main menu bar.

Options:
  • Inherits all from Box.
  • style.selected - Style for a selected item.
  • style.item - Style for an unselected item.
  • commands/items - Set buttons using an object with keys as titles of buttons, containing of objects containing keys of keys and callback.
  • autoCommandKeys - Automatically bind list buttons to keys 0-9.
Properties:
  • Inherits all from Box.
Events:
  • Inherits all from Box.
Methods:
  • Inherits all from Box.
  • setItems(commands) - Set commands (see commands option above).
  • add/addItem/appendItem(item, callback) - Append an item to the bar.
  • select(offset) - Select an item on the bar.
  • removeItem(child) - Remove item from the bar.
  • move(offset) - Move relatively across the bar.
  • moveLeft(offset) - Move left relatively across the bar.
  • moveRight(offset) - Move right relatively across the bar.
  • selectTab(index) - Select button and execute its callback.

Forms

Form (from Box)

A form which can contain form elements.

Options:
  • Inherits all from Box.
  • keys - Allow default keys (tab, vi keys, enter).
  • vi - Allow vi keys.
Properties:
  • Inherits all from Box.
  • submission - Last submitted data.
Events:
  • Inherits all from Box.
  • submit - Form is submitted. Receives a data object.
  • cancel - Form is discarded.
  • reset - Form is cleared.
Methods:
  • Inherits all from Box.
  • focusNext() - Focus next form element.
  • focusPrevious() - Focus previous form element.
  • submit() - Submit the form.
  • cancel() - Discard the form.
  • reset() - Clear the form.

Input (from Box)

A form input.

Textarea (from Input)

A box which allows multiline text input.

Options:
  • Inherits all from Input.
  • keys - Use pre-defined keys (i or enter for insert, e for editor, C-e for editor while inserting).
  • mouse - Use pre-defined mouse events (right-click for editor).
  • inputOnFocus - Call readInput() when the element is focused. Automatically unfocus.
Properties:
  • Inherits all from Input.
  • value - The input text. read-only.
Events:
  • Inherits all from Input.
  • submit - Value is submitted (enter).
  • cancel - Value is discared (escape).
  • action - Either submit or cancel.
Methods:
  • Inherits all from Input.
  • submit - Submit the textarea (emits submit).
  • cancel - Cancel the textarea (emits cancel).
  • readInput(callback) - Grab key events and start reading text from the keyboard. Takes a callback which receives the final value.
  • readEditor(callback) - Open text editor in $EDITOR, read the output from the resulting file. Takes a callback which receives the final value.
  • getValue() - The same as this.value, for now.
  • clearValue() - Clear input.
  • setValue(text) - Set value.

Textbox (from Textarea)

A box which allows text input.

Options:
  • Inherits all from Textarea.
  • secret - Completely hide text.
  • censor - Replace text with asterisks (*).
Properties:
  • Inherits all from Textarea.
  • secret - Completely hide text.
  • censor - Replace text with asterisks (*).
Events:
  • Inherits all from Textarea.
Methods:
  • Inherits all from Textarea.

Button (from Input)

A button which can be focused and allows key and mouse input.

Options:
  • Inherits all from Input.
Properties:
  • Inherits all from Input.
Events:
  • Inherits all from Input.
  • press - Received when the button is clicked/pressed.
Methods:
  • Inherits all from Input.
  • press() - Press button. Emits press.

Checkbox (from Input)

A checkbox which can be used in a form element.

Options:
  • Inherits all from Input.
  • checked - Whether the element is checked or not.
  • mouse - Enable mouse support.
Properties:
  • Inherits all from Input.
  • text - The text next to the checkbox (do not use setContent, use check.text = '').
  • checked - Whether the element is checked or not.
  • value - Same as checked.
Events:
  • Inherits all from Input.
  • check - Received when element is checked.
  • uncheck received when element is unchecked.
Methods:
  • Inherits all from Input.
  • check() - Check the element.
  • uncheck() - Uncheck the element.
  • toggle() - Toggle checked state.

RadioSet (from Box)

An element wrapping RadioButtons. RadioButtons within this element will be mutually exclusive with each other.

Options:
  • Inherits all from Box.
Properties:
  • Inherits all from Box.
Events:
  • Inherits all from Box.
Methods:
  • Inherits all from Box.

RadioButton (from Checkbox)

A radio button which can be used in a form element.

Options:
  • Inherits all from Checkbox.
Properties:
  • Inherits all from Checkbox.
Events:
  • Inherits all from Checkbox.
Methods:
  • Inherits all from Checkbox.

Prompts

Prompt (from Box)

A prompt box containing a text input, okay, and cancel buttons (automatically hidden).

Options:
  • Inherits all from Box.
Properties:
  • Inherits all from Box.
Events:
  • Inherits all from Box.
Methods:
  • Inherits all from Box.
  • input/setInput/readInput(text, value, callback) - Show the prompt and wait for the result of the textbox. Set text and initial value.

Question (from Box)

A question box containing okay and cancel buttons (automatically hidden).

Options:
  • Inherits all from Box.
Properties:
  • Inherits all from Box.
Events:
  • Inherits all from Box.
Methods:
  • Inherits all from Box.
  • ask(question, callback) - Ask a question. callback will yield the result.

Message (from Box)

A box containing a message to be displayed (automatically hidden).

Options:
  • Inherits all from Box.
Properties:
  • Inherits all from Box.
Events:
  • Inherits all from Box.
Methods:
  • Inherits all from Box.
  • log/display(text, [time], callback) - Display a message for a time (default is 3 seconds). Set time to 0 for a perpetual message that is dismissed on keypress.
  • error(text, [time], callback) - Display an error in the same way.

Loading (from Box)

A box with a spinning line to denote loading (automatically hidden).

Options:
  • Inherits all from Box.
Properties:
  • Inherits all from Box.
Events:
  • Inherits all from Box.
Methods:
  • Inherits all from Box.
  • load(text) - Display the loading box with a message. Will lock keys until stop is called.
  • stop() - Hide loading box. Unlock keys.

Data Display

ProgressBar (from Input)

A progress bar allowing various styles. This can also be used as a form input.

Options:
  • Inherits all from Input.
  • orientation - Can be horizontal or vertical.
  • style.bar - Style of the bar contents itself.
  • pch - The character to fill the bar with (default is space).
  • filled - The amount filled (0 - 100).
  • value - Same as filled.
  • keys - Enable key support.
  • mouse - Enable mouse support.
Properties:
  • Inherits all from Input.
Events:
  • Inherits all from Input.
  • reset - Bar was reset.
  • complete - Bar has completely filled.
Methods:
  • Inherits all from Input.
  • progress(amount) - Progress the bar by a fill amount.
  • setProgress(amount) - Set progress to specific amount.
  • reset() - Reset the bar.

Log (from ScrollableText)

A log permanently scrolled to the bottom.

Options:
  • Inherits all from ScrollableText.
  • scrollback - Amount of scrollback allowed. Default: Infinity.
  • scrollOnInput - Scroll to bottom on input even if the user has scrolled up. Default: false.
Properties:
  • Inherits all from ScrollableText.
  • scrollback - Amount of scrollback allowed. Default: Infinity.
  • scrollOnInput - Scroll to bottom on input even if the user has scrolled up. Default: false.
Events:
  • Inherits all from ScrollableText.
  • log - Emitted on a log line. Passes in line.
Methods:
  • Inherits all from ScrollableText.
  • log/add(text) - Add a log line.

Table (from Box)

A stylized table of text elements.

Options:
  • Inherits all from Box.
  • rows/data - Array of array of strings representing rows.
  • pad - Spaces to attempt to pad on the sides of each cell. 2 by default: one space on each side (only useful if the width is shrunken).
  • noCellBorders - Do not draw inner cells.
  • fillCellBorders - Fill cell borders with the adjacent background color.
  • style.header - Header style.
  • style.cell - Cell style.
Properties:
  • Inherits all from Box.
Events:
  • Inherits all from Box.
Methods:
  • Inherits all from Box.
  • setRows/setData(rows) - Set rows in table. Array of arrays of strings.
  table.setData([
    [ 'Animals',  'Foods'  ],
    [ 'Elephant', 'Apple'  ],
    [ 'Bird',     'Orange' ]
  ]);

Special Elements

Terminal (from Box)

A box which spins up a pseudo terminal and renders the output. Useful for writing a terminal multiplexer, or something similar to an mc-like file manager. Requires term.js and pty.js to be installed. See example/multiplex.js for an example terminal multiplexer.

Options:
  • Inherits all from Box.
  • handler - Handler for input data.
  • shell - Name of shell. $SHELL by default.
  • args - Args for shell.
  • cursor - Can be line, underline, and block.
  • terminal - Terminal name (Default: xterm).
  • env - Object for process env.
  • Other options similar to term.js'.
Properties:
  • Inherits all from Box.
  • term - Reference to the headless term.js terminal.
  • pty - Reference to the pty.js pseudo terminal.
Events:
  • Inherits all from Box.
  • title - Window title from terminal.
  • Other events similar to ScrollableBox.
Methods:
  • Inherits all from Box.
  • write(data) - Write data to the terminal.
  • screenshot([xi, xl, yi, xl]) - Nearly identical to element.screenshot, however, the specified region includes the terminal's entire scrollback, rather than just what is visible on the screen.
  • Other methods similar to ScrollableBox.

Image (from Box)

Display an image in the terminal (jpeg, png, gif) using either blessed's internal png/gif-to-terminal renderer (using a ANSIImage element) or using w3mimgdisplay (using a OverlayImage element).

Options:
  • Inherits all from Box.
  • file - Path to image.
  • type - ansi or overlay. Whether to render the file as ANSI art or using w3m to overlay. See the ANSIImage element for more information/options. (default: ansi).
Properties:
Events:
Methods:

ANSIImage (from Box)

Convert any .png file (or .gif, see below) to an ANSI image and display it as an element. This differs from the OverlayImage element in that it uses blessed's internal PNG/GIF parser and does not require external dependencies.

Blessed uses an internal from-scratch PNG/GIF reader because no other javascript PNG reader supports Adam7 interlaced images (much less pass the png test suite).

The blessed PNG reader supports adam7 deinterlacing, animation (APNG), all color types, bit depths 1-32, alpha, alpha palettes, and outputs scaled bitmaps (cellmaps) in blessed for efficient rendering to the screen buffer. It also uses some code from libcaca/libcucul to add density ASCII characters in order to give the image more detail in the terminal.

If a corrupt PNG or a non-PNG is passed in, blessed will display error text in the element.

.gif files are also supported via a javascript implementation (they are internally converted to bitmaps and fed to the PNG renderer). Any other image format is support only if the user has imagemagick (convert and identify) installed.

Options:
  • Inherits all from Box.
  • file - URL or path to PNG/GIF file. Can also be a buffer.
  • scale - Scale cellmap down (0-1.0) from its original pixel width/height (Default: 1.0).
  • width/height - This differs from other element's width or height in that only one of them is needed: blessed will maintain the aspect ratio of the image as it scales down to the proper number of cells. NOTE: PNG/GIF's are always automatically shrunken to size (based on scale) if a width or height is not given.
  • ascii - Add various "density" ASCII characters over the rendering to give the image more detail, similar to libcaca/libcucul (the library mplayer uses to display videos in the terminal).
  • animate - Whether to animate if the image is an APNG/animating GIF. If false, only display the first frame or IDAT (Default: true).
  • speed - Set the speed of animation. Slower: 0.0-1.0. Faster: 1-1000. It cannot go faster than 1 frame per millisecond, so 1000 is the fastest. (Default: 1.0)
  • optimization - mem or cpu. If optimizing for memory, animation frames will be rendered to bitmaps as the animation plays, using less memory. Optimizing for cpu will precompile all bitmaps beforehand, which may be faster, but might also OOM the process on large images. (Default: mem).
Properties:
  • Inherits all from Box.
  • img - Image object from the png reader.
  • img.width - Pixel width.
  • img.height - Pixel height.
  • img.bmp - Image bitmap.
  • img.cellmap - Image cellmap (bitmap scaled down to cell size).
Events:
  • Inherits all from Box.
Methods:
  • Inherits all from Box.
  • setImage(file) - Set the image in the box to a new path. File can be a path, url, or buffer.
  • clearImage() - Clear the image.
  • play() - Play animation if it has been paused or stopped.
  • pause() - Pause animation.
  • stop() - Stop animation.

OverlayImage (from Box)

Display an image in the terminal (jpeg, png, gif) using w3mimgdisplay. Requires w3m to be installed. X11 required: works in xterm, urxvt, and possibly other terminals.

Options:
  • Inherits all from Box.
  • file - Path to image.
  • ansi - Render the file as ANSI art instead of using w3m to overlay Internally uses the ANSIImage element. See the ANSIImage element for more information/options. (Default: true).
  • w3m - Path to w3mimgdisplay. If a proper w3mimgdisplay path is not given, blessed will search the entire disk for the binary.
  • search - Whether to search /usr, /bin, and /lib for w3mimgdisplay (Default: true).
Properties:
  • Inherits all from Box.
Events:
  • Inherits all from Box.
Methods:
  • Inherits all from Box.
  • setImage(img, [callback]) - Set the image in the box to a new path.
  • clearImage([callback]) - Clear the current image.
  • imageSize(img, [callback]) - Get the size of an image file in pixels.
  • termSize([callback]) - Get the size of the terminal in pixels.
  • getPixelRatio([callback]) - Get the pixel to cell ratio for the terminal.
  • Note: All methods above can be synchronous as long as the host version of node supports spawnSync.

Video (from Box)

A box which spins up a pseudo terminal in order to render a video via mplayer -vo caca or mpv --vo caca. Requires mplayer or mpv to be installed with libcaca support.

Options:
  • Inherits all from Box.
  • file - Video to play.
  • start - Start time in seconds.
Properties:
  • Inherits all from Box.
  • tty - The terminal element running mplayer or mpv.
Events:
  • Inherits all from Box.
Methods:
  • Inherits all from Box.

Layout (from Element)

A layout which can position children automatically based on a renderer method (experimental - the mechanics of this element may be changed in the future!).

By default, the Layout element automatically positions children as if they were display: inline-block; in CSS.

Options:
  • Inherits all from Element.
  • renderer - A callback which is called right before the children are iterated over to be rendered. Should return an iterator callback which is called on each child element: iterator(el, i).
  • layout - Using the default renderer, it provides two layouts: inline, and grid. inline is the default and will render akin to inline-block. grid will create an automatic grid based on element dimensions. The grid cells' width and height are always determined by the largest children in the layout.
Properties:
  • Inherits all from Element.
Events:
  • Inherits all from Element.
Methods:
  • Inherits all from Element.
  • renderer(coords) - A callback which is called right before the children are iterated over to be rendered. Should return an iterator callback which is called on each child element: iterator(el, i).
  • isRendered(el) - Check to see if a previous child element has been rendered and is visible on screen. This is only useful for checking child elements that have already been attempted to be rendered! see the example below.
  • getLast(i) - Get the last rendered and visible child element based on an index. This is useful for basing the position of the current child element on the position of the last child element.
  • getLastCoords(i) - Get the last rendered and visible child element coords based on an index. This is useful for basing the position of the current child element on the position of the last child element. See the example below.
Rendering a Layout for child elements
Notes

You must always give Layout a width and height. This is a chicken-and-egg problem: blessed cannot calculate the width and height dynamically before the children are positioned.

border and padding are already calculated into the coords object the renderer receives, so there is no need to account for it in your renderer.

Try to set position for children using el.position. el.position is the most primitive "to-be-rendered" way to set coordinates. Setting el.left directly has more dynamic behavior which may interfere with rendering.

Some definitions for coords (otherwise known as el.lpos):

  • coords.xi - the absolute x coordinate of the left side of a rendered element. It is absolute: relative to the screen itself.
  • coords.xl - the absolute x coordinate of the right side of a rendered element. It is absolute: relative to the screen itself.
  • coords.yi - the absolute y coordinate of the top side of a rendered element. It is absolute: relative to the screen itself.
  • coords.yl - the absolute y coordinate of the bottom side of a rendered element. It is absolute: relative to the screen itself.

Note again: the coords the renderer receives for the Layout already has border and padding subtracted, so you do not have to account for these. The children do not.

Example

Here is an example of how to provide a renderer. Note that this is also the default renderer if none is provided. This renderer will render each child as though they were display: inline-block; in CSS, as if there were a dynamically sized horizontal grid from left to right.

var layout = blessed.layout({
  parent: screen,
  top: 'center',
  left: 'center',
  width: '50%',
  height: '50%',
  border: 'line',
  style: {
    bg: 'red',
    border: {
      fg: 'blue'
    }
  },
  // NOTE: This is already the default renderer if none is provided!
  renderer: function(coords) {
    var self = this;

    // The coordinates of the layout element
    var width = coords.xl - coords.xi
      , height = coords.yl - coords.yi
      , xi = coords.xi
      , xl = coords.xl
      , yi = coords.yi
      , yl = coords.yl;

    // The current row offset in cells (which row are we on?)
    var rowOffset = 0;

    // The index of the first child in the row
    var rowIndex = 0;

    return function iterator(el, i) {
      // Make our children shrinkable. If they don't have a height, for
      // example, calculate it for them.
      el.shrink = true;

      // Find the previous rendered child's coordinates
      var last = self.getLastCoords(i);

      // If there is no previously rendered element, we are on the first child.
      if (!last) {
        el.position.left = 0;
        el.position.top = 0;
      } else {
        // Otherwise, figure out where to place this child. We'll start by
        // setting it's `left`/`x` coordinate to right after the previous
        // rendered element. This child will end up directly to the right of it.
        el.position.left = last.xl - xi;

        // If our child does not overlap the right side of the Layout, set it's
        // `top`/`y` to the current `rowOffset` (the coordinate for the current
        // row).
        if (el.position.left + el.width <= width) {
          el.position.top = rowOffset;
        } else {
          // Otherwise we need to start a new row and calculate a new
          // `rowOffset` and `rowIndex` (the index of the child on the current
          // row).
          rowOffset += self.children.slice(rowIndex, i).reduce(function(out, el) {
            if (!self.isRendered(el)) return out;
            out = Math.max(out, el.lpos.yl - el.lpos.yi);
            return out;
          }, 0);
          rowIndex = i;
          el.position.left = 0;
          el.position.top = rowOffset;
        }
      }

      // If our child overflows the Layout, do not render it!
      // Disable this feature for now.
      if (el.position.top + el.height > height) {
        // Returning false tells blessed to ignore this child.
        // return false;
      }
    };
  }
});

for (var i = 0; i < 10; i++) {
  blessed.box({
    parent: layout,
    width: i % 2 === 0 ? 10 : 20,
    height: i % 2 === 0 ? 5 : 10,
    border: 'line'
  });
}

Other

Helpers

All helpers reside on blessed.helpers or blessed.

  • merge(a, b) - Merge objects a and b into object a.
  • asort(obj) - Sort array alphabetically by name prop.
  • hsort(obj) - Sort array numerically by index prop.
  • findFile(start, target) - Find a file at start directory with name target.
  • escape(text) - Escape content's tags to be passed into el.setContent(). Example: box.setContent('escaped tag: ' + blessed.escape('{bold}{/bold}'));
  • parseTags(text) - Parse tags into SGR escape codes.
  • generateTags(style, text) - Generate text tags based on style object.
  • attrToBinary(style, element) - Convert style attributes to binary format.
  • stripTags(text) - Strip text of tags and SGR sequences.
  • cleanTags(text) - Strip text of tags, SGR escape code, and leading/trailing whitespace.
  • dropUnicode(text) - Drop text of any >U+FFFF characters.

Mechanics

Content & Tags

Every element can have text content via setContent. If tags: true was passed to the element's constructor, the content can contain tags. For example:

box.setContent('hello {red-fg}{green-bg}{bold}world{/bold}{/green-bg}{/red-fg}');

To make this more concise {/} cancels all character attributes.

box.setContent('hello {red-fg}{green-bg}{bold}world{/}');
Colors

Blessed tags support the basic 16 colors for colors, as well as up to 256 colors.

box.setContent('hello {red-fg}{green-bg}world{/}');

Tags can also use hex colors (which will be reduced to the most accurate terminal color):

box.setContent('hello {#ff0000-fg}{#00ff00-bg}world{/}');
Attributes

Blessed supports all terminal attributes, including bold, underline, blink, inverse, and invisible.

box.setContent('hello {bold}world{/bold}');
Alignment

Newlines and alignment are also possible in content.

box.setContent('hello\n'
  + '{right}world{/right}\n'
  + '{center}foo{/center}\n');
  + 'left{|}right');

This will produce a box that looks like:

| hello                 |
|                 world |
|          foo          |
| left            right |
Escaping

Escaping can either be done using blessed.escape()

box.setContent('here is an escaped tag: ' + blessed.escape('{bold}{/bold}'));

Or with the special {open} and {close} tags:

box.setContent('here is an escaped tag: {open}bold{close}{open}/bold{close}');

Either will produce:

here is an escaped tag: {bold}{/bold}
SGR Sequences

Content can also handle SGR escape codes. This means if you got output from a program, say git log for example, you can feed it directly to an element's content and the colors will be parsed appropriately.

This means that while {red-fg}foo{/red-fg} produces ^[[31mfoo^[[39m, you could just feed ^[[31mfoo^[[39m directly to the content.

Style

The style option controls most of the visual aspects of an element.

  style: {
    fg: 'blue',
    bg: 'black',
    bold: true,
    underline: false,
    blink: false,
    inverse: false,
    invisible: false,
    transparent: false,
    border: {
      fg: 'blue',
      bg: 'red'
    },
    scrollbar: {
      bg: 'blue'
    },
    focus: {
      bg: 'red'
    },
    hover: {
      bg: 'red'
    }
  }
Colors

Colors can be the names of any of the 16 basic terminal colors, along with hex values (e.g. #ff0000) for 256 color terminals. If 256 or 88 colors is not supported. Blessed with reduce the color to whatever is available.

Attributes

Blessed supports all terminal attributes, including bold, underline, blink, inverse, and invisible. Attributes are represented as bools in the style object.

Transparency

Blessed can set the opacity of an element to 50% using style.transparent = true;. While this seems like it normally shouldn't be possible in a terminal, blessed will use a color blending algorithm to blend the element of the foremost element with the background behind it. Obviously characters cannot be blended, but background colors can.

Shadow

Translucent shadows are also an option when it comes to styling an element. This option will create a 50% opacity 2-cell wide, 1-cell high shadow offset to the bottom-right.

shadow: true
Effects

Blessed supports hover and focus styles. (Hover is only useful is mouse input is enabled).

  style: {
    hover: {
      bg: 'red'
    },
    focus: {
      border: {
        fg: 'blue'
      }
    }
  }
Scrollbar

On scrollable elements, blessed will support style options for the scrollbar, such as:

style: {
  scrollbar: {
    bg: 'red',
    fg: 'blue'
  }
}

As a main option, scrollbar will either take a bool or an object:

scrollbar: {
  ch: ' '
}

Or:

scrollbar: true

Events

Events in Blessed work similar to the traditional node.js model, with one important difference: they have a concept of a tree and event bubbling.

Event Bubbling

Events can bubble in blessed. For example:

Receiving all click events for box (a normal event listener):

box.on('click', function(mouse) {
  box.setContent('You clicked ' + mouse.x + ', ' + mouse.y + '.');
  screen.render();
});

Receiving all click events for box, as well as all of its children:

box.on('element click', function(el, mouse) {
  box.setContent('You clicked '
    + el.type + ' at ' + mouse.x + ', ' + mouse.y + '.');
  screen.render();
  if (el === box) {
    return false; // Cancel propagation.
  }
});

el gets passed in as the first argument. It refers to the target element the event occurred on. Returning false will cancel propagation up the tree.

Positioning

Offsets may be a number, a percentage (e.g. 50%), or a keyword (e.g. center).

Dimensions may be a number, or a percentage (e.g. 50%).

Positions are treated almost exactly the same as they are in CSS/CSSOM when an element has the position: absolute CSS property.

When an element is created, it can be given coordinates in its constructor:

var box = blessed.box({
  left: 'center',
  top: 'center',
  bg: 'yellow',
  width: '50%',
  height: '50%'
});

This tells blessed to create a box, perfectly centered relative to its parent, 50% as wide and 50% as tall as its parent.

Percentages can also have offsets applied to them:

  ...
  height: '50%-1',
  left: '45%+1',
  ...

To access the calculated offsets, relative to the parent:

console.log(box.left);
console.log(box.top);

To access the calculated offsets, absolute (relative to the screen):

console.log(box.aleft);
console.log(box.atop);
Overlapping offsets and dimensions greater than parents'

This still needs to be tested a bit, but it should work.

Rendering

To actually render the screen buffer, you must call render.

box.setContent('Hello {#0fe1ab-fg}world{/}.');
screen.render();

Elements are rendered with the lower elements in the children array being painted first. In terms of the painter's algorithm, the lowest indicies in the array are the furthest away, just like in the DOM.

Artificial Cursors

Terminal cursors can be tricky. They all have different custom escape codes to alter. As an experimental alternative, blessed can draw a cursor for you, allowing you to have a custom cursor that you control.

var screen = blessed.screen({
  cursor: {
    artificial: true,
    shape: 'line',
    blink: true,
    color: null // null for default
  }
});

That's it. It's controlled the same way as the regular cursor.

To create a custom cursor:

var screen = blessed.screen({
  cursor: {
    artificial: true,
    shape: {
      bg: 'red',
      fg: 'white',
      bold: true,
      ch: '#'
    },
    blink: true
  }
});

Multiple Screens

Blessed supports the ability to create multiple screens. This may not seem useful at first, but if you're writing a program that serves terminal interfaces over http, telnet, or any other protocol, this can be very useful.

Server Side Usage

A simple telnet server might look like this (see examples/blessed-telnet.js for a full example):

var blessed = require('blessed');
var telnet = require('telnet2');

telnet({ tty: true }, function(client) {
  client.on('term', function(terminal) {
    screen.terminal = terminal;
    screen.render();
  });

  client.on('size', function(width, height) {
    client.columns = width;
    client.rows = height;
    client.emit('resize');
  });

  var screen = blessed.screen({
    smartCSR: true,
    input: client,
    output: client,
    terminal: 'xterm-256color',
    fullUnicode: true
  });

  client.on('close', function() {
    if (!screen.destroyed) {
      screen.destroy();
    }
  });

  screen.key(['C-c', 'q'], function(ch, key) {
    screen.destroy();
  });

  screen.on('destroy', function() {
    if (client.writable) {
      client.destroy();
    }
  });

  screen.data.main = blessed.box({
    parent: screen,
    left: 'center',
    top: 'center',
    width: '80%',
    height: '90%',
    border: 'line',
    content: 'Welcome to my server. Here is your own private session.'
  });

  screen.render();
}).listen(2300);

Once you've written something similar and started it, you can simply telnet into your blessed app:

$ telnet localhost 2300

Creating a netcat server would also work as long as you disable line buffering and terminal echo on the commandline via stty: $ stty -icanon -echo; ncat localhost 2300; stty icanon echo

Or by using netcat's -t option: $ ncat -t localhost 2300

Creating a streaming http 1.1 server than runs in the terminal is possible by curling it with special arguments: $ curl -sSNT. localhost:8080.

There are currently no examples of netcat/nc/ncat or http->curl servers yet.


The blessed.screen constructor can accept input, output, and term arguments to aid with this. The multiple screens will be managed internally by blessed. The programmer just has to keep track of the references, however, to avoid ambiguity, it's possible to explicitly dictate which screen a node is part of by using the screen option when creating an element.

The screen.destroy() method is also crucial: this will clean up all event listeners the screen has bound and make sure it stops listening on the event loop. Make absolutely certain to remember to clean up your screens once you're done with them.

A tricky part is making sure to include the ability for the client to send the TERM which is reset on the serverside, and the terminal size, which is should also be reset on the serverside. Both of these capabilities are demonstrated above.

For a working example of a blessed telnet server, see examples/blessed-telnet.js.

Notes

Windows Compatibility

Currently there is no mouse or resize event support on Windows.

Windows users will need to explicitly set term when creating a screen like so (NOTE: This is no longer necessary as of the latest versions of blessed. This is now handled automatically):

var screen = blessed.screen({ terminal: 'windows-ansi' });

Low-level Usage

This will actually parse the xterm terminfo and compile every string capability to a javascript function:

var blessed = require('blessed');

var tput = blessed.tput({
  terminal: 'xterm-256color',
  extended: true
});

process.stdout.write(tput.setaf(4) + 'Hello' + tput.sgr0() + '\n');

To play around with it on the command line, it works just like tput:

$ tput.js setaf 2
$ tput.js sgr0
$ echo "$(tput.js setaf 2)Hello World$(tput.js sgr0)"

The main functionality is exposed in the main blessed module:

var blessed = require('blessed')
  , program = blessed.program();

program.key('q', function(ch, key) {
  program.clear();
  program.disableMouse();
  program.showCursor();
  program.normalBuffer();
  process.exit(0);
});

program.on('mouse', function(data) {
  if (data.action === 'mousemove') {
    program.move(data.x, data.y);
    program.bg('red');
    program.write('x');
    program.bg('!red');
  }
});

program.alternateBuffer();
program.enableMouse();
program.hideCursor();
program.clear();

program.move(1, 1);
program.bg('black');
program.write('Hello world', 'blue fg');
program.setx((program.cols / 2 | 0) - 4);
program.down(5);
program.write('Hi again!');
program.bg('!black');
program.feed();

Testing

Most tests contained in the test/ directory are interactive. It's up to the programmer to determine whether the test is properly displayed. In the future it might be better to do something similar to vttest.

Examples

Examples can be found in examples/.

FAQ

  1. Why doesn't the Linux console render lines correctly on Ubuntu?
  • You need to install the ncurses-base package and the ncurses-term package. (#98)
  1. Why do vertical lines look chopped up in iTerm2?
  • All ACS vertical lines look this way in iTerm2 with the default font.
  1. Why can't I use my mouse in Terminal.app?
  • Terminal.app does not support mouse events.
  1. Why doesn't the OverlayImage element appear in my terminal?
  • The OverlayImage element uses w3m to display images. This generally only works on X11+xterm/urxvt, but it may work on other unix terminals.
  1. Why can't my mouse clicks register beyond 255 cells?
  • Older versions of VTE do not support any modern mouse protocol. On top of that, the old X10 protocol it does implement is bugged. Through several workarounds we've managed to get the cell limit from 127 to 255. If you're not happy with this, you may want to look into using xterm or urxvt, or a terminal which uses a modern VTE, like gnome-terminal.
  1. Is blessed efficient?
  • Yes. Blessed implements CSR and uses the painter's algorithm to render the screen. It maintains two screen buffers so it only needs to render what has changed on the terminal screen.
  1. Will blessed work with all terminals?
  • Yes. Blessed has a terminfo/termcap parser and compiler that was written from scratch. It should work with every terminal as long as a terminfo file is provided. If you notice any compatibility issues in your termial, do not hesitate to post an issue.
  1. What is "curses" and "ncurses"?
  • "curses" was an old library written in the early days of unix which allowed a programmer to easily manipulate the cursor in order to render the screen. "ncurses" is a free reimplementation of curses. It improved upon it quite a bit by focusing more on terminal compatibility and is now the standard library for implementing terminal programs. Blessed uses neither of these, and instead handles terminal compatibility itself.
  1. What is the difference between blessed and blessed-contrib?
  • blessed is a major piece of code which reimplements curses from the ground up. A UI API is then layered on top of this. blessed-contrib is a popular library built on top of blessed which makes clever use of modules to implement useful widgets like graphs, ascii art, and so on.
  1. Are there blessed-like solutions for non-javascript platforms?

Contribution and License Agreement

If you contribute code to this project, you are implicitly allowing your code to be distributed under the MIT license. You are also implicitly verifying that all code is your original work. </legalese>

License

Copyright (c) 2013-2015, Christopher Jeffrey. (MIT License)

See LICENSE for more info.

NPM DownloadsLast 30 Days