iced-rs/iced

Lifecycle diagram

Open

#222 opened on Mar 17, 2020

View on GitHub
 (6 comments) (1 reaction) (0 assignees)Rust (30,491 stars) (1,572 forks)batch import
documentationgood first issueimprovementquestion

Description

Thank this awesome project that has made cross-platform UI development an easier way in the Rust world.

I know iced is just at a very early stage, we don't have enough good docs yet. We can get started through a set of examples. However, after insight a lot of examples, I still can't get a clear concept and relationship of every single component, such as the Application's lifecycle, when and how frequency the view() and update() get called, how State, Element and Message, etc interact. So, just hoping we have a lifecycle or relationship diagram for brevity clarification to the developer. Maybe the Android Activity lifecycle, Vue lifecycle diagrams are such a good instance.

image

Contributor guide

Tech stack
rust
Domain
documentation
Issue type
documentation
DifficultyEstimated implementation difficulty for a new contributor, from 1 for very small changes to 5 for expert-level work.
3
Estimated timeA rough time range for an experienced contributor to investigate, implement, test, and prepare a pull request.
1-2 days
Activity statusHow available the issue appears right now: fresh, active, stale, blocked, or waiting on maintainer input.
stale
ClarityHow clearly the issue explains the expected change, acceptance criteria, and next step.
clear
Prerequisites
Basic RustFamiliarity with Iced examples
Newbie friendlinessA 1-100 score estimating how approachable this issue is for first-time contributors.
60
Research direction
Study the Iced source code, specifically the `Application` trait in `src/application.rs`, the `view` and `update` functions, and the widget system in `src/widget.rs`. Review existing examples to understand the component interactions. Look at the `State`, `Element`, and `Message` types. Create a diagram similar to the Android Activity lifecycle, showing when `view` and `update` are called, and how messages flow. Consider using tools like Mermaid or draw.io.