diff options
| author |  Héctor Ramón <hector0193@gmail.com> | 2019-10-25 23:21:50 +0200 |
|---|---|---|
| committer |  GitHub <noreply@github.com> | 2019-10-25 23:21:50 +0200 |
| commit | 5e3cfb358ec1bfe7d6e3cfc73d64bb3196e78f50 (patch) | |
| tree | c7074be659f618bc4577f7fae6427ad13f46da2a /ROADMAP.md | |
| parent | e3cf59fd99ad96e47e00a9434c01da8bc2942bc9 (diff) | |
| download | iced-5e3cfb358ec1bfe7d6e3cfc73d64bb3196e78f50.tar.gz iced-5e3cfb358ec1bfe7d6e3cfc73d64bb3196e78f50.tar.bz2 iced-5e3cfb358ec1bfe7d6e3cfc73d64bb3196e78f50.zip | |
Clarify event subscriptions in `ROADMAP`
Diffstat (limited to 'ROADMAP.md')
| -rw-r--r-- | ROADMAP.md | 2 |
1 files changed, 1 insertions, 1 deletions
@@ -191,7 +191,7 @@ Besides performing async actions on demand, most applications also need to liste The idea here is to also follow [Elm]'s footsteps. We can add a method `subscriptions(&self) -> Subscription<Message>` to `Application` and keep the subscriptions alive in the runtime. -The challenge here is designing the public API of subscriptions, so users can build their own, and _subscription diffing_, or basically detecting when a subscription is added/changed/removed. For this, we can take a look at the source code of [Elm] for inspiration. +The challenge here is designing the public API of subscriptions. Ideally, users should be able to create their own subscriptions and the GUI runtime should keep them alive by performing _subscription diffing_ (i.e. detecting when a subscription is added, changed, or removed). For this, we can take a look at [Elm] for inspiration. ### Layers Currently, Iced assumes widgets cannot be laid out on top of each other. We should implement support for multiple layers of widgets. |