No description
Find a file
2025-02-04 01:21:10 +01:00
.cargo Fix new clippy lints 2024-12-02 19:56:27 +01:00
.github Bump MSRV to 1.82 2025-01-27 00:59:17 +01:00
benches Update wgpu to 22.0 2024-09-20 00:14:47 +02:00
core Introduce Levitating variant for mouse::Cursor 2025-02-03 05:45:51 +01:00
docs Redirect docs.iced.rs to actual docs 2024-05-07 21:38:31 +02:00
examples Fix broken references when parsing markdown streams 2025-02-02 04:01:57 +01:00
futures Implement time::repeat and simplify Subscription::run_with 2025-01-24 16:45:18 +01:00
graphics Introduce LineEnding to editor and fix inconsistencies 2025-01-28 06:23:38 +01:00
highlighter Implement markdown incremental code highlighting 2025-01-31 20:37:07 +01:00
renderer Support custom renderers in iced_test through renderer::Headless trait 2024-12-14 03:49:24 +01:00
runtime Use simple quote in runtime::window docs 2025-01-16 11:21:11 +00:00
src Enable animation module for Wasm target 2025-01-29 04:55:51 +01:00
test Fix redundant expression in iced_test documentation 2024-12-17 04:32:49 +01:00
tiny_skia Support custom renderers in iced_test through renderer::Headless trait 2024-12-14 03:49:24 +01:00
wgpu Add debug assertions to draw_mesh in wgpu renderer 2025-02-04 01:21:10 +01:00
widget Introduce Levitating variant for mouse::Cursor 2025-02-03 05:45:51 +01:00
winit Fix infinite runtime loop when queue redraws at a specific time 2025-02-02 02:28:04 +01:00
.gitignore Track Cargo.lock for reproducible builds and tests 2024-12-17 03:09:52 +01:00
Cargo.lock Fix broken references when parsing markdown streams 2025-02-02 04:01:57 +01:00
Cargo.toml Fix broken references when parsing markdown streams 2025-02-02 04:01:57 +01:00
CHANGELOG.md Bump version to 0.13.1 🎉 2024-09-19 07:05:51 +02:00
clippy.toml Increase threshold of enum-variant-names lint 2023-09-07 07:50:59 +02:00
CONTRIBUTING.md Remove broken links to ECOSYSTEM.md 2024-09-21 21:20:20 +02:00
Cross.toml Rely on GHCR instead of Docker Hub in Cross.toml 2022-01-26 21:22:54 +07:00
DEPENDENCIES.md Add a flake for a dev shell 2025-01-30 22:37:49 +02:00
LICENSE Add LICENSE 2019-08-01 15:43:19 +02:00
README.md Showcase halloy and icebreaker in README 🎉 2024-09-18 22:38:45 +02:00
ROADMAP.md Remove broken links to ECOSYSTEM.md 2024-09-21 21:20:20 +02:00
rustfmt.toml Update Rust edition to 2021 🎉 2022-02-09 17:57:44 +07:00

Iced

Documentation Crates.io License Downloads Test Status Discourse Discord Server

A cross-platform GUI library for Rust focused on simplicity and type-safety. Inspired by Elm.

Features

Iced is currently experimental software. Take a look at the roadmap and check out the issues.

Overview

Inspired by The Elm Architecture, Iced expects you to split user interfaces into four different concepts:

  • State — the state of your application
  • Messages — user interactions or meaningful events that you care about
  • View logic — a way to display your state as widgets that may produce messages on user interaction
  • Update logic — a way to react to messages and update your state

We can build something to see how this works! Let's say we want a simple counter that can be incremented and decremented using two buttons.

We start by modelling the state of our application:

#[derive(Default)]
struct Counter {
    value: i32,
}

Next, we need to define the possible user interactions of our counter: the button presses. These interactions are our messages:

#[derive(Debug, Clone, Copy)]
pub enum Message {
    Increment,
    Decrement,
}

Now, let's show the actual counter by putting it all together in our view logic:

use iced::widget::{button, column, text, Column};

impl Counter {
    pub fn view(&self) -> Column<Message> {
        // We use a column: a simple vertical layout
        column![
            // The increment button. We tell it to produce an
            // `Increment` message when pressed
            button("+").on_press(Message::Increment),

            // We show the value of the counter here
            text(self.value).size(50),

            // The decrement button. We tell it to produce a
            // `Decrement` message when pressed
            button("-").on_press(Message::Decrement),
        ]
    }
}

Finally, we need to be able to react to any produced messages and change our state accordingly in our update logic:

impl Counter {
    // ...

    pub fn update(&mut self, message: Message) {
        match message {
            Message::Increment => {
                self.value += 1;
            }
            Message::Decrement => {
                self.value -= 1;
            }
        }
    }
}

And that's everything! We just wrote a whole user interface. Let's run it:

fn main() -> iced::Result {
    iced::run("A cool counter", Counter::update, Counter::view)
}

Iced will automatically:

  1. Take the result of our view logic and layout its widgets.
  2. Process events from our system and produce messages for our update logic.
  3. Draw the resulting user interface.

Read the book, the documentation, and the examples to learn more!

Implementation details

Iced was originally born as an attempt at bringing the simplicity of Elm and The Elm Architecture into Coffee, a 2D game library I am working on.

The core of the library was implemented during May 2019 in this pull request. The first alpha version was eventually released as a renderer-agnostic GUI library. The library did not provide a renderer and implemented the current tour example on top of ggez, a game library.

Since then, the focus has shifted towards providing a batteries-included, end-user-oriented GUI library, while keeping the ecosystem modular.

Contributing / Feedback

If you want to contribute, please read our contributing guidelines for more details.

Feedback is also welcome! You can create a new topic in our Discourse forum or come chat to our Discord server.

Sponsors

The development of Iced is sponsored by the Cryptowatch team at Kraken.com