ratatui-wgpu 0.1.0

A wgpu based backend for ratatui.
Documentation 
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43

# ratatui-wgpu

A wgpu based rendering backend for ratatui.

This started out as a custom rendering backend for a game I'm developing, and I thought I'd make it
available to the broader community as an alternative rendering target for TUI applications. One of
its primary goals is to support serving TUI applications on the web.

## Alternatives

- [egui_ratatui](https://crates.io/crates/egui_ratatui) uses an egui widget as its backend, allowing
  it to run anywhere egui can run (including the web).
  - Advantages: Egui is significantly more mature than this library and brings with it a host of
    widgets and builtin accessibility support.
  - Disadvantages: You can't run custom shader code against its output.

## Goals

The crate has the following goals in order of descending priority.
1. Allow custom shader code to be run against rendered text.
    - See [`PostProcessor`] for details. You can also see the implementation of the
      [`shaders::DefaultPostProcessor`] or the `hello_pipeline` example for a demonstration of how
      this works.
2. Target WASM.
    - You will likely want to enable the `web` feature if you intend to support Firefox.
3. Correct text rendering (including shaping).
    - This library relies on [swash](https://crates.io/crates/swash) for shaping and layout. Swash
      allows this library to handle most things I've tested it on, although it breaks down when
      presented with complex sequences of combining characters (e.g. zalgo text).
4. Reasonable performance.

## Non-goals

1. Builtin-accessibility support.
   - I'm willing to make concessions to enable accessibility (the native version of my game uses
     accesskit), but integrating directly with accessibility libraries is outside the scope of this
     library.

## Known Limitations

1. No support for rtl text.
2. No support for text blinking.
   - I'm open to adding this, but I have no use for it. This complicates the web story slightly,
     since browsers don't support [`std::time`].
3. No cursor rendering.
    - The location of the cursor is tracked, and operations using it should behave as expected, but
      the cursor is not rendered to the screen.