iq-scm / ribir Goto Github PK

Ribir is a framework for building modern native/wasm cross-platform user interface applications.

Documents | Examples

• Non-injection and Non-invasive: Ribir interacts with the APIs of your data structure, and does not require you to do any pre-design for the user interface. Developers can focus on designing the data struct, logic and APIs. Ribir will neither break your existing logic nor require injecting any of its own objects.

• Declarative: The user interface is the description of data, the description will automatically react to the data modification. Once you describe your data, the description will keep describing your data.

• Purely composed: Ribir creates UI via widgets. There is not a base-object, even if the built-in fields are provided in a composed way. For example, only if you use margin field, the Margin widget will be composed, if you do not use it, you don't pay any overhead for Margin. "Only pay for what you need" is an important guideline for Ribir.

use ribir::prelude::*;
fn main() {
  app::run(widget! {
    states { cnt: Stateful::new(0) }
    Column {
      h_align: HAlign::Center,
      align_items: Align::Center,
      FilledButton { on_tap: move |_| *cnt += 1, Label::new("Add") }
      H1 { text: cnt.to_string() }
      FilledButton { on_tap: move |_| *cnt += -1, Label::new("Sub") }
    }
  });
}

More Examples

• Write once run anywhere: Compile native code for desktop and mobile(not yet), and WASM for Web(not yet). Since Ribir has rather few platform dependencies, it's not hard to support more platforms by yourself.
• Declarative language expanded from Rust syntax: The declarative language is based on Rust, so interaction with Rust becomes natural and easy.
• Easy custom widget: Ribir supports the implementation of custom Compose, Render and ComposeChild widgets, you only need to implement the corresponding traits. Evenmore, you are able to specify the template of the children of ComposeChild, just by deriving the Template traits.
• Powerful custom theme: Specify the theme for the whole application or partial subtree. In the theme, you can configure the palette, icons, animate transitions, widget custom themes, the interactive behavior of widget and even compose more decoration widgets on it.
• Rich available official widgets: A ribir_widgets library exists，containing common desktop and mobile widgets.
• No side effect animations: Animation in Ribir is only a visual effect, that won't affect data. Animate support for any render widgets.
• Alternative rendering backends: The rendering backend is replaceable, you can implement your own rendering to output image, html, svg or any other stuff. Ribir provides developers with a gpu backend basing on wgpu and perhaps a soft(cpu) render in the future.

We are grateful to the community for contributing bug fixes and improvements.

😎 New to Ribir?

Start learning about the framework by helping us improve our documentation. Feel free to open a new "Documentation" issue. We are also very welcome:

• Point out to us where our document has misunderstandings
• Pull requests which improve test coverage
• Add undocumented code (e.g. built-in widget)
• Report typo

For more information please read：

• Contributing Guide
• Writing a Good Issue

🤔 Confused about something?

Feel free to go to Discussions and open a new "Q&A" to get help from contributors. Often questions lead to improvements to the ergonomics of the framework, better documentation, and even new features!

😱 Found a bug?

Please report all bugs! We are happy to help support developers fix the bugs they find if they are interested and have the time.

This project exists thanks to all the people who contribute:

We also found inspiration from the following frameworks:

• Flutter
• QML

Ribir is MIT licensed