osui-rs/docs
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

Fixed link issues

Browse Source
This commit is contained in:
selimaj-dev
2026-01-31 22:10:51 +01:00
parent 50fea916ce
commit efda07bac5
11 changed files with 41 additions and 43 deletions
Download Patch File Download Diff File Expand all files Collapse all files
versioned_docs/version-0.1.1/01-guides/creating-custom-widgets.md
+1 -1
View File
@@ -4,7 +4,7 @@ While OSUI provides a rich set of built-in elements, you'll often need to create
## The `Element` Trait Revisited
As discussed in [Concepts: Widget Model](/docs/concepts/widget-model), the `Element` trait is the contract for anything that can be rendered.
As discussed in [Concepts: Widget Model](/docs/0.1.1/concepts/widget-model), the `Element` trait is the contract for anything that can be rendered.
```rust
pub trait Element: Send + Sync {
versioned_docs/version-0.1.1/01-guides/getting-started-example.md
+5 -5
View File
@@ -4,7 +4,7 @@ This guide expands on the basic "Hello, OSUI!" example to demonstrate a slightly
## 1. Project Setup (Review)
Ensure you have a new Rust project set up and `osui` added to your `Cargo.toml`. Refer to the [Getting Started](/docs/) guide if you haven't done this already.
Ensure you have a new Rust project set up and `osui` added to your `Cargo.toml`. Refer to the [Getting Started](/docs/0.1.1/) guide if you haven't done this already.
## 2. The `main.rs` File
@@ -145,10 +145,10 @@ pub fn app(screen: Arc<Screen>) -> Rsx {
* Whenever `count` is marked as changed, the `DynWidget` associated with that `Div` automatically rebuilds its content and triggers a re-render in the next frame. This is why the number updates in the UI.
4. **`rsx!` Macro**:
* The `rsx!` macro provides a declarative way to define your UI tree. It creates a hierarchy of `Widget`s, each potentially containing an `Element` and various `Component`s.
* `Paginator`, `FlexRow`, `FlexCol`, `Div`, `Heading`, `Input` are built-in [elements](/docs/reference/elements) that define structure and appearance.
* `@Transform` and `@Style` are [components](/docs/reference/style) that attach layout and visual properties to elements.
* `@Handler` is a [component](/docs/reference/extensions) that allows a widget to listen for specific events (here, `crossterm::event::Event`).
* `@Focused` and `@AlwaysFocused` are [components](/docs/reference/extensions/focus) from `RelativeFocusExtension` that manage input focus.
* `Paginator`, `FlexRow`, `FlexCol`, `Div`, `Heading`, `Input` are built-in [elements](/docs/0.1.1/reference/elements) that define structure and appearance.
* `@Transform` and `@Style` are [components](/docs/0.1.1/reference/style) that attach layout and visual properties to elements.
* `@Handler` is a [component](/docs/0.1.1/reference/extensions) that allows a widget to listen for specific events (here, `crossterm::event::Event`).
* `@Focused` and `@AlwaysFocused` are [components](/docs/0.1.1/reference/extensions/focus) from `RelativeFocusExtension` that manage input focus.
5. **`screen.run()`**: This method starts the main application loop. It continuously:
* Renders all widgets.
* Processes events from extensions.