No description
Find a file
Héctor Ramón e0da42efed
Merge pull request #2556 from dtoniolo/docs
Document how the state of a `Component` can be managed
2024-09-13 22:50:59 +02:00
.cargo Merge branch 'master' into wgpu/better-architecture 2024-04-07 14:06:52 +02:00
.github Upgrade upload-artifact action in build workflow 2024-09-10 18:09:13 +02:00
benches Fix clippy lints in wgpu benchmark 2024-05-08 20:34:31 +02:00
core Merge pull request #2551 from airstrike/mouse-interactions 2024-09-13 17:07:56 +02:00
docs Redirect docs.iced.rs to actual docs 2024-05-07 21:38:31 +02:00
examples Fix examples/multitouch dividing by zero 2024-09-13 01:29:35 +02:00
futures Fix lints for Rust 1.80 2024-07-26 11:01:33 +02:00
graphics Merge pull request #2575 from m4rch3n1ng/rm-clone-trait-bound 2024-09-13 02:02:49 +02:00
highlighter Fix newlines in highlighter and markdown example 2024-07-18 22:55:40 +02:00
renderer Add stroke_rectangle 2024-09-10 23:44:04 +02:00
runtime Add mouse passthrough tasks to window module 2024-09-05 11:13:37 +02:00
src Expose additional subscription types in advanced 2024-07-30 22:22:28 +02:00
tiny_skia Leverage stroke for stroke_rectangle in tiny-skia backend 2024-09-10 23:45:33 +02:00
wgpu Merge pull request #2484 from vladh/fix-radii-typo 2024-09-11 00:43:50 +02:00
widget Document how the state of a Component can be managed 2024-09-13 22:41:43 +02:00
winit Merge pull request #2551 from airstrike/mouse-interactions 2024-09-13 17:07:56 +02:00
.gitignore Create cargo lint alias 2023-09-20 04:07:20 +02:00
Cargo.toml Introduce image-without-codecs feature flag 2024-09-02 11:47:55 +02:00
CHANGELOG.md Update CHANGELOG 2024-02-22 17:39:46 +01:00
clippy.toml Increase threshold of enum-variant-names lint 2023-09-07 07:50:59 +02:00
CONTRIBUTING.md Fix link in CONTRIBUTING guide 2023-09-11 01:10:31 +02:00
Cross.toml Rely on GHCR instead of Docker Hub in Cross.toml 2022-01-26 21:22:54 +07:00
DEPENDENCIES.md actually wayland.dev isn't needed 2024-06-16 10:42:21 +00:00
ECOSYSTEM.md refactored window storage; 2023-07-21 13:53:38 -07:00
LICENSE Add LICENSE 2019-08-01 15:43:19 +02:00
README.md Reference "Examples" header in examples link in the README 2024-05-27 21:33:00 +02:00
ROADMAP.md Link to graphical roadmap in ROADMAP.md 2023-07-26 20:21:59 +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, check out the issues, and feel free to contribute!

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 engine 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:

The Iced Ecosystem

Contributing / Feedback

Contributions are greatly appreciated! 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