package notty-community

All checked builds pass
  1. Overview
  2. Docs

Description

Notty is a declarative terminal library for OCaml structured around a notion of composable images. It tries to abstract away the basic terminal programming model, providing something simpler and more expressive.

This is a branch from the original notty, maintained by the community.

Added to opam-repository:

README

Notty — Declaring terminals

Notty is a declarative terminal library for OCaml structured around a notion of composable images. It tries to abstract away the basic terminal programming model, providing something simpler and more expressive.

The core layout engine and IO codecs are pure platform-independent OCaml. Distribution includes modules with input and output facilities for Unix, and Lwt on Unix.

As an attempt to redefine terminal programming, Notty has to be opinionated. It assumes Unicode throughout, does not have universal support for various terminals out there, and has a peculiar programming and rendering model.

Notty's core API was heavily influenced by Haskell's Vty.

Where to start

Check out the documentation, examples, or peek directly into the interface file.

Building with dune build @ex will produce several little example programs that also double as tests.

(* Game of Life with ZX Spectrum kitsch. *)

let dot : image = I.uchar A.(fg lightred) (Uchar.of_int 0x25cf) 1 1

let background step (n, m) =
  let k = 24. *. sin (float (step + m + n) /. 10.) |> truncate in
  if k > 0 then I.char A.(fg (gray k)) '.' 1 1 else I.void 1 1

let render (w, h) step life : image =
  I.tabulate w (h - 1) @@ fun x y ->
    let pt = (x, y) in
    if CSet.mem pt life then dot else background step pt

What?

  • Notty?

    Terminals are tedious to program for. Notty tries to abstract the tedium away, leaving you with a more pleasant programming surface that's quite unlike a TTY. Hence, No-TTY.

  • A new kind of Rust terminal?

    This Notty has no connection to any other body of code named Notty.

  • Why make yet another terminal output library?

    Because:

    • It allows one to describe what should be seen, as opposed to commanding a terminal.
    • It's pretty compact. Both bells and whistles can be implemented separately.
    • Core is easy to glue onto various IO backends.
    • Pure platform-independent OCaml.

Dependencies (4)

  1. uutf >= "1.0.0"
  2. cppo build & >= "1.1.0"
  3. ocaml >= "4.08.0"
  4. dune >= "3.0"

Dev Dependencies (3)

  1. odoc with-doc
  2. lwt with-test
  3. uucp with-dev-setup

Optional Dependencies (1)

  1. lwt

Conflicts (1)

  1. lwt < "2.6.0"

Build status

Results of building notty-community with each compiler on check.ci.ocaml.org, run of against opam-repository 8d8d144. All results for this package.

Each result links to its build log. To keep crawlers from overloading the site, build logs require a GitHub sign-in (see ocurrent/opam-health-check). On your first log, GitHub asks you to “Authorize opam-health-check”, the OCurrent app that runs these checks; it sees only your public profile, not your repositories. The sign-in lasts 30 days.

Version OCaml 4.11 OCaml 4.14 OCaml 5.2 OCaml 5.4 OCaml 5.5
0.2.4 (this version) good good good good good
  • good Package successfully built
  • partial One of the dependencies failed to build
  • bad Package failed to build
  • n/a Package is not available in this environment
  • internal Internal failure