iced-yoda/pure/Cargo.toml

[package]
name = "iced_pure"
version = "0.2.2"
edition = "2021"
description = "Pure widgets for Iced"
license = "MIT"
repository = "https://github.com/iced-rs/iced"
documentation = "https://docs.rs/iced_pure"
keywords = ["gui", "ui", "graphics", "interface", "widgets"]
categories = ["gui"]

[dependencies]
iced_native = { version = "0.5", path = "../native" }
iced_style = { version = "0.4", path = "../style" }
num-traits = "0.2"
Draft `iced_virtual` subcrate The idea here is to expose a set of "virtual widgets" that can be used with a `Virtual` widget and its `virtual::State`. A virtual widget is a widget that does not contain any state, but instead is a "virtual" representation of the "real" widget. The real widgets are stored in the `virtual::State`. Every time a new virtual widget tree is created during `view`, it is compared to the previous one and "real" widgets are added / removed to the `virtual::State`. Effectively, this removes the need to keep track of local widget state in the application state and allows `view` to take an immutable reference to `self`. To summarize, using this crate should allow users to remove `State` structs in their application state. Eventually, the strategy used here may be adopted generally and, as a result, all of the widgets in `iced_native` would be replaced! 2022-02-09 19:42:15 +07:00			`[package]`
Rename `iced_virtual` to `iced_pure` `virtual` is a reserved keyword in Rust :grimacing: 2022-02-11 17:50:12 +07:00			`name = "iced_pure"`
Bump versions :tada: 2022-05-31 05:40:39 +02:00			`version = "0.2.2"`
Draft `iced_virtual` subcrate The idea here is to expose a set of "virtual widgets" that can be used with a `Virtual` widget and its `virtual::State`. A virtual widget is a widget that does not contain any state, but instead is a "virtual" representation of the "real" widget. The real widgets are stored in the `virtual::State`. Every time a new virtual widget tree is created during `view`, it is compared to the previous one and "real" widgets are added / removed to the `virtual::State`. Effectively, this removes the need to keep track of local widget state in the application state and allows `view` to take an immutable reference to `self`. To summarize, using this crate should allow users to remove `State` structs in their application state. Eventually, the strategy used here may be adopted generally and, as a result, all of the widgets in `iced_native` would be replaced! 2022-02-09 19:42:15 +07:00			`edition = "2021"`
Bump versions :tada: 2022-05-02 21:53:25 +02:00			`description = "Pure widgets for Iced"`
			`license = "MIT"`
			`repository = "https://github.com/iced-rs/iced"`
			`documentation = "https://docs.rs/iced_pure"`
			`keywords = ["gui", "ui", "graphics", "interface", "widgets"]`
			`categories = ["gui"]`
Draft `iced_virtual` subcrate The idea here is to expose a set of "virtual widgets" that can be used with a `Virtual` widget and its `virtual::State`. A virtual widget is a widget that does not contain any state, but instead is a "virtual" representation of the "real" widget. The real widgets are stored in the `virtual::State`. Every time a new virtual widget tree is created during `view`, it is compared to the previous one and "real" widgets are added / removed to the `virtual::State`. Effectively, this removes the need to keep track of local widget state in the application state and allows `view` to take an immutable reference to `self`. To summarize, using this crate should allow users to remove `State` structs in their application state. Eventually, the strategy used here may be adopted generally and, as a result, all of the widgets in `iced_native` would be replaced! 2022-02-09 19:42:15 +07:00
			`[dependencies]`
Bump versions :tada: 2022-05-02 21:53:25 +02:00			`iced_native = { version = "0.5", path = "../native" }`
			`iced_style = { version = "0.4", path = "../style" }`
Implement `Slider` in `iced_pure` 2022-02-13 17:20:10 +07:00			`num-traits = "0.2"`