HEAD Latest release released

Linux CI Version License


Crysterm is a console/terminal toolkit for Crystal.

At the moment it follows closely the implementation and behavior of the libraries that inspired it, Blessed and Blessed-contrib for Node.js. However, being implemented in Crystal (an OO language), it tries to use the language's best practices, avoid bugs and problems found in Blessed, and also (especially in the future) incorporate some aspects of Qt.

Trying it out

git clone
cd crysterm
shards --ignore-crystal-version

export TERM=xterm-256color

crystal examples/
crystal examples/
crystal examples/


Animated demo

Crysterm Demo Video

Layout engine (showing inline/masonry layout)

Crysterm Masonry Layout

Transparency, color blending, shadow

Crysterm Color Blending



As mentioned, Crysterm is inspired by Blessed, Blessed-contrib, and Qt.

Blessed is a large, self-contained framework. Apart from implementing Blessed, its authors have also implemented all the necessary/prerequisite components, including an event model (a modified copy of an early Node.js EventEmitter), complete termcap/terminfo system (parsing, compilation, output, and input from terminal devices; in a word an alternative to ncurses), all types of mouse support, Unicode handling, color manipulation routines, etc. However, these implementations have been mixed with the rest of source code, reducing the potential for their reuse.

In Crysterm, the equivalents of those components have been created as individual shards, making them available to the whole Crystal ecosystem. The event model has been implemented in event_handler, color routines in term_colors, terminal output in, and terminfo library in represents Crystal's bindings for a C terminfo library called unibilium, now maintained by Neovim. The package exists for a good number of operating systems and distributions, and one only needs the binary library installed, not headers. There is also a mostly working Crystal-native terminfo library available in but, due to other priorities, trying to use that instead of unibilium is not planned. Both unibilium and native terminfo implementation for Crystal were initially implemented by Benoit de Chezelles (@bew).)

Crysterm closely follows Blessed, and copies of Blessed's comments have been included in Crysterm's sources for easier correlation and search between code, files, and features. A copy of Blessed's repository also exists in docelic/blessed-clean. It is a temporary repository in which files are deleted after their contents are reviewed and discarded or implemented in Crysterm.

High-level development plan for Crysterm looks as follows:

  1. Improving Crysterm itself (fixing bugs, replacing strings with better data types (enums, classes, etc.), and doing new development).
  2. Porting everything of value remaining in blessed-clean (most notably: reading terminfo command responses from terminal, mouse support, artificial cursor, full unicode (graphemes), and a number of widgets)
  3. Porting over widgets & ideas from blessed-contrib
  4. Developing more line-oriented features. Currently Crysterm is suited for full-screen app development. It would be great if line-based features were added, and if then various small line-based utilities that exist as shards/apps for Crystal would be ported to become Crysterm's line- or screen-based widgets
  5. Adding features and principles from Qt

Those are generalal guidelines. For smaller, more specific development/contribution tasks, grep sources for "TODO", "NOTE", and "XXX", see file TODO, and see general Crystal wishlist in file CRYSTAL-WISHLIST.

Event model

Event model is at the very core of Crysterm, implemented via event_handler.

Please refer to event_handler's documentation for all usage instructions.

The events used by Crysterm and its widgets are defined in src/

Class Hierarchy

  1. Top-level class is Display. It represents a physical device / terminal used for @input and @output (Blessed calls this Program)
  2. Each display can have one or more Screens (Blessed also calls this Screen). Screens are always full-screen and represent the whole surface of a Display
  3. Each screen can have one or more Widgets, arranged appropriately to implement final apps

The default Display and Screen do not need to be created explicitly if you don't need to change any of their options. They will be created automatically if missing when the first Widget is created.

Widgets can be added and positioned on the screen directly, but some widgets are particularly suitable for containing or arranging other/child widgets. Most notably this is the Layout widget which can auto-size and auto-position contained widgets in the form of a grid or inline (masonry-like) layout (LayoutType::{Grid,Inline}).

There are currently no widgets that would represent GUI windows like QWindow or QMainWindow in Qt (having title bar, menu bar, status bar, etc.), but implementing them is planned. (Windows too will inherit from Widget.)

All mentioned classes include event_handler for event-based behavior.

Positioning and Layouts

Crysterm Widget

Widget positions and sizes work like in Blessed. They can be specified as numbers (e.g. 10), percentages (e.g. "10%"), both (e.g. "10%+2"), or specific keywords ("center", which has an effect of 50% - self.width_or_height//2, or "resizable" which adjusts in runtime).

That model is simple and works quite OK, although it is not as developed as the model in Qt. For example, there is no way to shrink or grow widgets disproportionally when window is resized, and there is no way to define maximum or minimum size. (Well, minimum size calculation does exist for resizable widgets, but only for trying to find the minimum size based on actual contents, rather than programmer's wishes. (What we call "resizable" is called "shrink" in Blessed, even though it can also grow.))

Speaking of layouts, the one layout engine currently existing, Widget::Layout, is equivalent to Blessed's. It can arrange widgets in a grid-like or masonry-like style. There are no equivalents of Qt's QBoxLayout.

The positioning and layout code is very manageable; adding new Qt-like or other features is not a big task. (Whether various layouts would then still inherit from Widget or not (like they don't in Qt) is open for consideration.)

Finally, worth noting, there are currently some differences in the exact types or combinations of mentioned values supported for top, left, width, height, align, and valign. It would be good if all these could be adjusted to accept the same flexible/unified specification, and if the list of supported specifications would even grow over time. (For example, one could want to pass a block or proc, in which case it'd be called to get the value.)

Rendering and Drawing

Screens contain widgets. To make screens appear on display with all the expected contents and current state, one calls Screen#render. This function calls Widget#render on each of immediate child elements, which results in the final/rendered state reflected in internal memory.

At the end of rendering, Screen#draw is automatically called which makes any changes in internal state appear on the display. For efficiency, painter's algorithm is used, only changes ("damage") are rendered, and renderer can optionally make use of CSR (change-scroll-region) and/or BCE (back-color-erase) optimizations (see OptimizationFlag).

Calling render whereever appropriate is not a concern because there is code making sure that render runs at most once per unit of time (currently 1/29th of a second) and all accumulated changes are rendered in one pass.

When state has been set up for the first time and the program is to start running the display, one generally calls Display#exec. This renders the specified (or default) screen and starts running the program.

Text Attributes and Colors

Crysterm implements its own concept of "tags" in strings, such as "{lightblue-fg} text in light blue {/lightblue-fg}". Tags can be embedded in strings directly, applied from a Hash with generate_tags, or removed from a string with strip_tags or clean_tags. Any existing strings where "{}" should not be interpreted can be protected with escape_tags.

The supported tags are: {center}, {left}, and {right} for alignment, {normal | default}, {bold}, {underline | underlined | ul}, {blink}, {inverse}, and {invisible} for text attributes, {COLOR-fg} and {COLOR-bg} for colors, and {/} for closing all open tags.

Supported COLOR names are: default, black, blue, bright-black, bright-blue, bright-cyan, bright-gray, bright-green, bright-grey, bright-magenta, bright-red, bright-white, bright-yellow, cyan, gray, green, grey, light-black, light-blue, light-cyan, light-gray, light-green, light-grey, light-magenta, light-red, light-white, light-yellow, magenta, red, white, yellow.

In addition to the above color names, one can also specify colors by color index (syntax: ID-...), or by RGB hex notation using the 16M color palette (syntax #RRGGBB-.... 16M RGB is the recommented way to define colors, and Crysterm will automatically reduce them to 256, 16, 8, or 2 colors if/when needed, depending on terminal capabilities.

One could also define foreground and background colors and attributes by manually embedding the appropriate escape sequences into strings or using Crystal's Colorize module. Crysterm is interoperable with those approaches.


Every Widget has an attribute style, defining the colors and attributes to use during rendering. If no style is explicitly defined, the default style is instantiated. Apart from styling the widget itself, each Style may have overriding style definitions for widget's possible subelements (border, scrollbar, shadow, track, bar, item, header, cell, label) and states (focus, blur, hover, selected).

If any of these subelements have more specific settings which define substantial behavior and not just visual aspects, they are defined as properties directly on the widget (e.g. Widget#border, Widget#scrollbar, etc.). These properties also serve as toggles that turn on or off respective elements.

The final goal (still to be implemented) is to be able to define one or a couple Style instances which would apply to, and style, all widgets. Additionally, these definitions would be serializable to YAML, enabling convenient theming.


By default, for development, frames-per-second value is displayed at the bottom of every Screen. When displaying FPS is enabled, Crysterm measures time needed to complete rendering and drawing cycles, and displays them as "R/D/FPS" (estimated renderings per second, drawings per second, and total/combined frames per second).

Because the rendering+drawing cycle happens up to 29 times per second, the FPS value should stay above 30 of frame skipping could occur.


Run crystal spec as usual.

More specs need to be added.

One option for testing, currently not used, would be to support a way where all output (terminal sequences etc.) is written to an IO which is a file. Then simply the contents of that file are compared with a known-good snapshot.

This would allow testing complete programs and a bunch of functionality at once, efficiently.


Run crystal docs as usual.

Notable Differences

List of notable differences (hopefully improvements) compared to Blessed:

  • Program has been renamed to Display (representing a physical display managed by Crysterm)
  • Element and Node have been renamed and consolidated into Widget
  • Screen no longer inherits from Widget
  • As such, Screen is not a top-level parent of any Widget; use [@]screen to get Screen or parent_or_screen for parent or screen
  • auto_padding, tab_size, and tabc are properties on Widget instead of Screen
  • Event names have been changed from strings to classes, e.g. event "scroll" is ::Crysterm::Event::Scroll
  • tags alias for parse_tags option has been removed; use parse_tags: true/false. Default is true
  • All terminal-level stuff is in shard Tput, not Crysterm
  • style property has been consolidated; all style-related stuff is under widget's @style : Style
  • Widget property shadow also accepts Float64, in addition to true which defaults to drawing shadow with alpha=0.5
  • Style property transparent has been renamed to transparency and also accepts Float64, in addition to true which defaults to 0.5
  • In Widget::ProgressBar, the display of value is done using foreground color. This is different than Blessed, and arguably more correct
  • In Crysterm, default border type is "line" (BorderType::Line). In Blessed it is "bg"
  • In Blessed, there is variable ignore_dock_contrast, which if set to true will cause borders to always be docked, or if set to false it will not dock borders of different colors. In Crysterm, this variable is defined as @dock_contrast: DockContrast, and DockContrast is an enum that can be Ignore, DontDock, or Blend. The first two behave like Blessed's true and false respectively, and Blend is a new option that blends colors.

List of current bugs / quirks in Crysterm, in no particular order:

  • It is likely that Crysterm's API interface and general usability could be improved in many places. Fortunately those are easy improvements and/or suggestions that can be made by early users and adopters
  • Screen's top-level widgets need to be added to Screen with screen.append widget explicitly (option screen: screen to doesn't do everything it should at the moment)
  • Items need to be added to Widget::List explicitly, after list creation (option items: [...] to isn't available at the moment)
  • Widget::Layout needs explicit width and height (e.g. "100%"). It seems this isn't needed in Blessed
  • Widget::TextArea lacks many features (deficiency inherited from Blessed)
  • Scrollbar on a widget can be enabled with scrollbar: true. Styling for the scrollbar column is taken from @style.track and for the scrollbar character from @style.scrollbar. This is inherited from Blessed and unintuitive. style.scrollbar should be the column, and style.track (or other name) should be the scroll position indicator.
  • Some parts of code are marked with "D O:" or "E O:". These mean "Disabled Originally" and "Enabled Originally", indicating whether respective parts of code were disabled or enabled "originally" (in Blessed sources). Those marked with "D O:" do not need any work unless they were part of unfinished improvements in Blessed, in which case they probably should be developed/enhanced in Crysterm.

If you notice any problems or have any suggestions, please submit an issue.


  • All the fine folks on Libera.Chat IRC channel #crystal-lang and on Crystal's Gitter channel

Other projects

List of interesting or similar projects in no particular order:


  • - Readline-esque library with fancy features
  • - Library for drawing graphics on the console screen
  • - Bindings, wrapper, and utilities for termbox


  • - Crystal's built-in module Colorize
  • - Rainbow spec formatter for Crystal
  • - Make working with colors in Crystal fun!
  • - Terminal output styling
  • - Color representation conversion methods (rgb, hsv, hsl, ...) for Crystal
  • - Crystal toy app for colorizing LS output


  • - Event model used by Crysterm
  • - Event-centric pub/sub model for objects inspired by the Qt framework
  • - Idiomatic asynchronous event-driven architecture


  • - Type-safe, object-oriented option parser
  • - Simple terminal spinner
  • - Draw ascii character tables in the terminal
  • - Lightweight console ASCII line charts
  github: crystallabs/crysterm
License AGPLv3
Crystal 1.0.0


Dependencies 6

  • ameba ~> 0.13.0
    {'github' => 'crystal-ameba/ameba', 'version' => '~> 0.13.0'}
  • crystallabs-helpers ~> 1.0
    {'github' => 'crystallabs/', 'version' => '~> 1.0'}
  • event_handler ~> 1.0
    {'github' => 'crystallabs/event_handler', 'version' => '~> 1.0'}
  • term_colors ~> 1.0
    {'github' => 'crystallabs/term_colors', 'version' => '~> 1.0'}
  • tput master
    {'branch' => 'master', 'github' => 'crystallabs/tput'}
  • w3m_image_display
    {'github' => 'SamualLB/w3mimagedisplay'}

Development Dependencies 0

Dependents 0

Last synced .
search fire star recently