me/iced
1
0
Fork 0
Code Issues Pull requests Projects Releases Packages Wiki Activity
iced/native
History
Nikolai Vazquez 267e242238 Make many functions const 
The point is to set up repeated components or boilerplate before their
use sites.

The majority of these make sense as `const`. However, some functions
such as those regarding state may not make sense as `const`.
2019-11-29 21:24:52 -05:00
..
src Make many functions const 2019-11-29 21:24:52 -05:00
Cargo.toml Add installation section to subcrate READMEs 2019-11-20 09:56:16 +01:00
CHANGELOG.md Add CHANGELOG to subcrates 2019-11-25 14:55:14 +01:00
README.md Add installation section to subcrate READMEs 2019-11-20 09:56:16 +01:00

README.md

iced_native

Documentation Crates.io License project chat

iced_native takes iced_core and builds a native runtime on top of it, featuring:

  • A custom layout engine, greatly inspired by druid
  • Event handling for all the built-in widgets
  • A renderer-agnostic API

To achieve this, it introduces a bunch of reusable interfaces:

  • A Widget trait, which is used to implement new widgets: from layout requirements to event and drawing logic.
  • A bunch of Renderer traits, meant to keep the crate renderer-agnostic.
  • A Windowed trait, leveraging raw-window-handle, which can be implemented by graphical renderers that target windows. Window-based shells (like iced_winit) can use this trait to stay renderer-agnostic.

iced_native

Installation

Add iced_native as a dependency in your Cargo.toml:

iced_native = "0.1.0"

Iced moves fast and the master branch can contain breaking changes! If you want to learn about a specific release, check out the release list.