Crates.io | prettygooey |
lib.rs | prettygooey |
version | 0.1.1 |
source | src |
created_at | 2023-12-06 22:19:24.297659 |
updated_at | 2023-12-10 17:16:34.536856 |
description | Set of themed UI components for the iced GUI library |
homepage | |
repository | https://github.com/pieterdd/prettygooey |
max_upload_size | |
id | 1060468 |
size | 102,210 |
Prettygooey is a set of themed UI components for the iced GUI library. Works on Windows, Linux and Mac.
⚠️ Prettygooey, like iced, is experimental software. ⚠️
The official iced book was fairly short at the time of writing, so my limited knowledge was pieced together from docs.rs snippets, reading source code and visiting their forums.
The simplest way to create a GUI in iced is with an iced::Sandbox
. It kind of behaves like a window. You'll have to implement four methods:
new
: intialize your default state heretitle
: controls the title of the windowupdate
: more on this laterview
: renders your widgetsIced, like many GUI frameworks, works with containers (i.e. groups of widgets) and widgets. Containers help you lay out your widgets, and common examples of them include a row or a column. Containers can contain containers, too.
Suppose you want to create a confirmation dialog. Such a layout would probably have the following structure:
When using vanilla iced widgets, this would look something like this:
Row and column containers have some useful modifier functions:
spacing
adds a gap between your widgets to let your layout breathe.padding
adds spacing on the outside of the container. This keeps your text from sticking to the side of the window.Here's a simple example putting the above into practice:
fn view(&self) -> Element<'_, Self::Message> {
column!(
text("Are you sure?"),
row![button("Yes"), button("No")].spacing(10)
)
.spacing(20)
.padding(10)
.into()
}
You've defined your UI, but it won't show up until you invoke it. In the example below, we initialize a window with mostly default settings.
MySandbox::run(Settings {
window: window::Settings {
size: (400, 450),
position: Position::Centered,
..window::Settings::default()
},
..Settings::default()
})
You can find the full list of available settings here.
Many widgets allow for some kind of user interaction. Examples include your garden variety button, text input or checkbox. These interactions produce events. For a checkbox, a typical interaction plays out like this:
update
function reacts to that new state by updating the variable to the new stateYou get to decide what the event looks like. Your Sandbox can designate a specific enum as its Message type. For example:
#[derive(Debug, Clone)]
enum SpaceshipSandboxMessage {
BoostersEnabledChanged(bool),
ShieldSelectionChanged(Shield),
CommanderNameChanged(String),
RebootButtonPressed,
}
In the case of a checkbox, you set the event as follows:
let chk_enable_boosters = checkbox(
"Enable boosters",
self.enable_boosters,
Self::Message::BoostersEnabledChanged,
);
Your Sandbox's update
function will be called whenever such an event is emitted. There you can respond accordingly:
fn update(&mut self, message: Self::Message) {
match message {
Self::Message::BoostersEnabledChanged(value) => {
self.enable_boosters = value;
}
}
}
In your Sandbox's constructor, create an instance of prettygooey::theme::Theme
. You'll use this object to instantiate Prettygooey widgets.
fn new() -> Self {
Self {
theme: Theme {
accent_color: AccentColor::Magenta,
},
}
}
In your Sandbox's view
function, return an instance of our primary container to apply the background.
fn view(&self) -> Element<'_, Self::Message> {
// Pass a row or column of widgets to the container
self.theme.primary_container(column![]).into()
}
All supported widgets can be created via the Theme instance.
let button = self.theme.button("Click me");
Prettygooey widgets may provide optional customizations. Take the Text widget for example. By importing the extension trait prettygooey::theme::TextExt
, you expose a variant
method that'll let you switch the variant to Dimmed:
self.theme
.text("Theme selection")
.variant(TextVariant::Dimmed),
For a list of available widgets with screenshots and examples, see the code docs.
If you'd like to see more than a few loose snippets, check out the showcase example. It's the source code for the screenshot at the top of the README.
Pop! OS's libcosmic implements a much wider range of iced widgets and is backed by device manufacturer System76. On the other hand, libcosmic's learning curve may be a bit steeper. The library is primarily intended for use by applications that are native to the Cosmic desktop environment.
That said, I'd still check it out and make up your own mind.