r3bl_rs_utils_core

Why R3BL?

R3BL TUI library & suite of apps focused on developer productivity

We are working on building command line apps in Rust which have rich text user interfaces (TUI). We want to lean into the terminal as a place of productivity, and build all kinds of awesome apps for it.

1. 🔮 Instead of just building one app, we are building a library to enable any kind of rich TUI development w/ a twist: taking concepts that work really well for the frontend mobile and web development world and re-imagining them for TUI & Rust.

   • Taking inspiration from things like React, SolidJS, Elm, iced-rs, Jetpack Compose, JSX, CSS, but making everything async (so they can be run in parallel & concurrent via Tokio).
   • Even the thread running the main event loop doesn't block since it is async.
   • Using proc macros to create DSLs to implement something inspired by CSS & JSX.

2. 🌎 We are building apps to enhance developer productivity & workflows.

   • The idea here is not to rebuild tmux in Rust (separate processes mux'd onto a single terminal window). Rather it is to build a set of integrated "apps" (or "tasks") that run in the same process that renders to one terminal window.
   • Inside of this terminal window, we can implement things like "app" switching, routing, tiling layout, stacking layout, etc. so that we can manage a lot of TUI apps (which are tightly integrated) that are running in the same process, in the same window. So you can imagine that all these "app"s have shared application state (that is in a Redux store). Each "app" may also have its own Redux store.
   • Here are some examples of the types of "app"s we want to build:
     1. multi user text editors w/ syntax highlighting
     2. integrations w/ github issues
     3. integrations w/ calendar, email, contacts APIs

All the crates in the r3bl-open-core repo provide lots of useful functionality to help you build TUI (text user interface) apps, along w/ general niceties & ergonomics that all Rustaceans 🦀 can enjoy 🎉.

Table of contents

• Introduction
• Changelog
• Learn how these crates are built, provide feedback

Introduction

This crate provides lots of low level functionality like Unicode strings (that support emoji), text styling, and more.

It is a dependency of the following crates:

1. r3bl_tui
2. r3bl_tuify
3. r3bl_terminal_async
4. r3bl_cmdr
5. r3bl_rs_utils_macro (procedural macros)
6. r3bl_redux
7. r3bl_rs_utils

Due to the requirements of proc macros being in a separate crate, this breakdown of one crate into multiple crates is necessary:

1. Put some code in a separate crate (r3bl_rs_utils_core) that is used by other crates.
2. Put the proc macros in a separate crate (r3bl_rs_utils_macro). This crate also depends on the r3bl_rs_utils_core crate.
3. Finally, make the "public" crate (r3bl_rs_utils) depend on the other two. However, this r3bl_rs_utils crate isn't really used anymore. It is possible to simply add a dependency on the r3bl_rs_utils_core crate directly, and r3bl_tui for instance.

As a way to hide this kind of layering from the users of the "main" r3bl_rs_utils crate, all the modules tend to be re-exported, making them available from the "main" or top-level crate; more info on this here.

Changelog

Please check out the changelog to see how the library has evolved over time.

Learn how these crates are built, provide feedback

To learn how we built this crate, please take a look at the following resources.

• If you like consuming video content, here's our YT channel. Please consider subscribing.
• If you like consuming written content, here's our developer site. Please consider subscribing to our newsletter.
• If you have questions, please join our discord server.

License: Apache-2.0