No description
Find a file
Héctor d94c080dd4
Merge pull request #2988 from andymandias/text-font_maybe
Add `font_maybe` Utility Function to `Text`
2025-11-27 04:42:50 +01:00
.cargo Fix new clippy lints 2024-12-02 19:56:27 +01:00
.github Add iced_test to document workflow 2025-10-17 22:19:24 +02:00
beacon Group primitive timings in Present span 2025-05-06 04:17:06 +02:00
benches Add advanced shaping benchmark to benches::wgpu 2025-10-31 16:12:45 +01:00
core Merge pull request #2988 from andymandias/text-font_maybe 2025-11-27 04:42:50 +01:00
debug Fix Send requirements in WebAssembly builds 2025-08-29 09:07:19 +02:00
devtools Remove push_maybe from stack widget 2025-09-23 02:23:12 +02:00
docs Rename iced_sentinel to iced_beacon and refactor its API 2024-05-10 20:08:09 +02:00
examples Use seconds helper in tooltip example 2025-11-27 04:15:34 +01:00
futures Replace doc_auto_cfg with doc_cfg 2025-10-08 04:37:13 +02:00
graphics Merge pull request #2979 from DKolter/issue_2976 2025-11-27 04:38:15 +01:00
highlighter Run cargo fmt 2025-02-21 01:37:13 +01:00
program Remove missing_debug_implementations lint 2025-09-12 05:25:09 +02:00
renderer Replace Raw in core::text::Renderer with a new Renderer trait 2025-11-26 00:41:05 +01:00
runtime Convert URL into a hyperlink in runtime::window 2025-11-25 23:26:55 +01:00
selector Use to_owned instead of to_string in iced_selector 2025-11-18 23:05:30 +01:00
src Export InputMethod type directly in advanced module 2025-11-25 10:45:25 +01:00
test Take Program by reference in iced_test::screenshot 2025-11-12 14:34:48 +01:00
tester Simplify windowing server features a bit 2025-11-25 08:38:59 +01:00
tiny_skia Merge pull request #2977 from DKolter/issue_2934 2025-11-27 04:41:16 +01:00
wgpu Improve naming in layer modules 2025-11-26 00:45:07 +01:00
widget Add explicit Open state to tooltip widget 2025-11-27 04:29:24 +01:00
winit Add allow_automatic_tabbing task to runtime::window 2025-11-25 23:15:22 +01:00
.gitignore Track Cargo.lock for reproducible builds and tests 2024-12-17 03:09:52 +01:00
Cargo.lock Make syntect use fancy-regex instead of onig 2025-11-25 22:53:01 +01:00
Cargo.toml Make syntect use fancy-regex instead of onig 2025-11-25 22:53:01 +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 clean up devShell templates 2025-11-21 02:30:38 +01: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 all examples to Rust 2024 2025-02-21 01:37:14 +01: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