xilem_extras

KO | EN

gitlite — search

#javascript #python #hacktoberfest #react #ai #typescript #llm #go #golang #android #machine-learning #rust #deep-learning #linux

(★ 12)

In this repository higher level controls are offered, like a tree view, tables, editors which can be used with xilem in rust

xilem_extras Latest Version Download

Download Latest Version (.zip)

// repository documentation

Was this content helpful?

★ 0 (0 ratings)

# xilem_extras

High-level widget library for [Xilem](https://github.com/linebender/xilem) providing Tree, List, Table, and Menu widgets with SwiftUI-inspired APIs.

***This crate is highly experimental and a sandbox project for me and not for productive use. The API may break anytime. Use it at your own risk. It is used to try ideas and concepts. Also AI may be used to create sketches. It's marked then in the commit message. This project is not related to xilem or the team, even though the name includes "xilem." The purpose of this playground is to explore xilem so that well-balanced and refined concepts can later be submitted as single pull requests to the original xilem repository. If you create a xilem project, please use the original xilem reposity. Participation is optional. However, please do not consider this repository an official extension of xilem. Claude Code has been used to handle the arabic language, exotic operating systems like windows and for refactoring tasks.***

## Overview

This library extends Xilem with common UI patterns for building desktop applications. It provides composable, trait-based widgets that integrate seamlessly with Xilem's reactive architecture. It is still experimental. But you can already use it to build Applications. This is no official xilem package. 
But I try to keep it up to date and compatible to Xilem.

## Design approach

Software is usually programmed *inductively*. You start by creating a structure. You begin with the core and add elements bit by bit until the whole thing comes together. The Xilem team at Liebender does this very well. I had the idea to experiment with higher-level controls. After several attempts, however, I failed. Then it occurred to me that you can’t just build tree views or tables based on an idea alone. What struck me more was that these controls could be developed based on a real-world application—to discover, through practical experience, the application itself, and "day-to-day work," which features and parameter lists are needed.

That’s why I decided to build this sandbox project. So the approach is *deductively*. I start at the high level and work *quick and dirty* at the beginning so that I can get into the real application very quickly. As I work with my own applications on a daily basis, I find myself needing to adapt the xilem layer for my needs. I start by working backward. Once I’ve fully understood everything, I try to dig deeper and write a foundation in Masonry. This crate works. And you can already use it to program real applications. However, *the project is primarily intended as a lab*. Feel free to use it for real applications. But let me be very clear: *this is not intended to be a final product*. Rather, it is meant to help understanding design patterns so that one can finally create a clean Rust interface for Xilem and Masonry.

## Roadmap

### Level 1 - Playground (AI can be used)

- [x] Create a reasonable amount of controls so that a useful apprication can be built
- [x] Experiment with these controls to find a useful working interface for xilem

### Level 2 - Trial and Error (AI can be used)

- [x] Move stuff around, try, optimize, refactor
- [x] Cleanup 1: Split Masonry and Xilem so that it matches the original xilem folder scheme.
- [ ] Fix bugs
- [ ] Review functionality. Make sure most functionality is done in Masonry and just called from xilem.

### Level 3 - Make it perfect (From here on only humans are allowed to write and review code! AI is forbidden)

- [ ] Review naming, traits, signatures
- [ ] Fix bugs
- [ ] Cleanup 2
- [ ] Prepare a first release bundle
- [ ] Create pull requests for each widget at the official xilem repository. 
- [ ] Delete widgets from here which have been accepted by xilem.

## Available Widgets

- **Tree Group** - Hierarchical data group for DIY groups.
- **Tree View** - Hierarchical data with expand/collapse, selection, and keyboard navigation
- **List View** - Selectable lists with sections and disclosure groups
- **Table View** - Sortable data grids with resizable columns and multi-column sorting
- **Menu Button** - Pulldown menus with separators
- **App Menu** - Pulldown menus with nested sub menus fpr limnux, and muda for MacOS and Windows.
- **Dropdown Select** - Value selection dropdowns
- **Tabs** - Tab bar with closeable tabs
- **Calendar Picker** - Pick a date.
- **Styled Widget** - Wrapped xilem widgets, which can have a style. You can switch dark and bright modes.
- **Modal Overlay** - Sometimes you need a modal sheet. It's there
- **Progress Bars** - Tinted, color gradient, monochrome. Linear or circular. Busy indicator.
- **Chart** - Simple chat to represent numeric data
- **Stock Chart** - The classic with candle stick, bar, line and a value picker crosshair.

## Quick Start

```bash
just run
```

This runs the gallery with all features enabled. [Just](https://github.com/casey/just) is a command runner. Install it with:

```bash
cargo install just
```

Or directly without just:

```bash
cargo run --example gallery --features "rust-logos app-menu"
```

The `rust-logos` feature provides Rust file icons, and `app-menu` enables native menu bar support (muda on macOS/Windows).

## Core Traits

The library uses trait-based design for flexibility:

```rust
// Stable identity for collections
pub trait Keyed {
    type Key: Clone + Eq + Hash + Send + 'static;
    fn key(&self) -> Self::Key;
}

// Hierarchical data
pub trait TreeNode: Keyed + Sized {
    fn children(&self) -> &[Self];
    fn is_expandable(&self) -> bool;
    fn label(&self) -> &str;
}

// Selection strategy
pub trait SelectionState<Id: Clone + Eq + Hash> {
    fn is_selected(&self, id: &Id) -> bool;
    fn select(&mut self, id: Id, modifiers: SelectionModifiers);
    fn clear(&mut self);
}
```

## Selection Types

- `SingleSelection<Id>` - One item at a time, toggle on re-click
- `MultiSelection<Id>` - Cmd/Ctrl+click toggle, Shift+click range

## Sort Descriptors

Table sorting uses Rust's iterator pattern:

```rust
let sorted = sort_order.sorted(&cyclists);
let filtered = sort_order.filter_sorted(&cyclists, |c| c.joy_level >= 8);
```

## Examples

### Tree Group

```rust
use xilem_extras::{tree_group, TreeAction, ExpansionState, SingleSelection};

tree_group(
    &model.file_tree,           // root node (implements TreeNode)
    &model.expansion,           // ExpansionState<NodeId>
    Some(&model.selection),     // Option<&impl SelectionState<NodeId>>
    |node, depth, is_expanded, is_selected| {
        // Build row view for each node
        flex_row((
            if node.is_expandable() {
                disclosure(is_expanded).boxed()
            } else {
                sized_box(()).width(16.0).boxed()
            },
            label(node.label()),
        ))
        .padding_left(depth as f64 * 16.0)
        .background_color(if is_selected { BG_SELECTED } else { Color::TRANSPARENT })
        .boxed()
    },
    |state, node_id, action| {
        match action {
            TreeAction::Toggle => state.expansion.toggle(node_id),
            TreeAction::Select => state.selection.set(Some(node_id.clone())),
            TreeAction::DoubleClick => state.open_file(node_id),
        }
    },
)
```

### Row Button with Multi-Selection

Use `row_button_with_modifiers` to capture Cmd/Ctrl+Click for multi-selection:

```rust
use xilem_extras::{row_button_with_modifiers, SelectionState, SelectionModifiers};

fn contact_row(contact: &Contact, selected: bool) -> impl WidgetView<AppModel> {
    let id = contact.id;
    let row = flex_row((
        label(contact.name.clone()),
        label(contact.email.clone()),
    ));

row_button_with_modifiers(row, move |model: &mut AppModel, modifiers| {
        // Convert platform modifiers to SelectionModifiers
        // (Cmd on macOS, Ctrl on Windows/Linux)
        let sel_mods = SelectionModifiers::from_modifiers(modifiers);
        model.selection.select(id, sel_mods);
    })
    .hover_bg(BG_HOVER)
    .background_color(if selected { BG_SELECTED } else { Color::TRANSPARENT })
}
```

### Menu Button

```rust
use xilem_extras::{menu_button, menu_item, separator};

### Context Menu

```rust
use xilem_extras::{context_menu, menu_item, separator};

### App Menu Bar (xilem_muda)

The `app_menu` module provides a unified API for application menu bars:
- **macOS/Windows**: Native menus via the muda crate (requires `app-menu` feature)
- **Linux**: Fallback using `menu_button` widgets

**Builder API** (for defining menu structure):

```rust
use xilem_extras::{MenuBarBuilder, Key, CMD, SHIFT};

// Define menu structure with the fluent builder API
let menu_def = MenuBarBuilder::new()
    .menu("File", |m| m
        .item("New", |s: &mut AppState| s.new_file())
            .shortcut(CMD + Key::N)
        .item("Open...", |s| s.open_file())
            .shortcut(CMD + Key::O)
        .separator()
        .submenu("Recent", |m| m
            .item("project1.rs", |s| s.open_recent(0))
            .item("project2.rs", |s| s.open_recent(1))
        )
        .separator()
        .item("Quit", |s| s.quit())
            .shortcut(CMD + Key::Q)
    )
    .menu("Edit", |m| m
        .item("Undo", |s| s.undo())
            .shortcut(CMD + Key::Z)
            .enabled(|s| s.can_undo())
        .item("Redo", |s| s.redo())
            .shortcut(CMD + SHIFT + Key::Z)
            .enabled(|s| s.can_redo())
    );
```

**Xilem Widget Rendering** (for Linux and cross-platform fallback):

```rust
use xilem_extras::{menu_button, menu_item, separator, submenu};
use xilem::view::{flex_row, label};

// Build application menu bar with menu_button widgets
fn build_menu_bar(model: &mut AppModel) -> impl WidgetView<AppModel> {
    flex_row((
        menu_button(
            label("File"),
            (
                menu_item("New", |m: &mut AppModel| m.new_file()),
                menu_item("Open...", |m| m.open_file()),
                separator(),
                submenu("Recent", (
                    menu_item("project1.rs", |m| m.open_recent(0)),
                    menu_item("project2.rs", |m| m.open_recent(1)),
                )),
                separator(),
                menu_item("Quit", |m| m.quit()),
            ),
        ),
        menu_button(
            label("Edit"),
            (
                menu_item("Undo", |m: &mut AppModel| m.undo()),
                menu_item("Redo", |m| m.redo()),
            ),
        ),
    ))
    .background_color(MENU_BAR_BG)
}
```

**Shortcut DSL**:

```rust
use xilem_extras::{Key, CMD, SHIFT, ALT, CTRL};

// Platform-aware shortcuts
CMD + Key::S           // Cmd+S on macOS, Ctrl+S on Windows/Linux
CMD + SHIFT + Key::Z   // Cmd+Shift+Z / Ctrl+Shift+Z
ALT + Key::F4          // Alt+F4 (always Alt)
CTRL + Key::C          // Ctrl+C (always Ctrl, even on macOS)
```

### List

```rust
use xilem_extras::{list_styled, ListAction, ListStyle};

list_styled(
    &model.contacts,
    &model.selection,
    ListStyle::new().hover_bg(BG_HOVER),
    |contact, is_selected| {
        // Build row view - clone data, don't borrow
        let name = contact.name.clone();
        flex_row((label(name),))
            .background_color(if is_selected { BG_SELECTED } else { Color::TRANSPARENT })
    },
    |state, action| {
        match action {
            ListAction::Select(id, mods) => state.selection.select(id, mods),
            ListAction::Activate(id) => state.open_contact(&id),
        }
    },
)
```

### Table

```rust
use xilem_extras::{table, table_cell, column, TableAction, Alignment};

table(
    &model.employees,
    &[
        column("name", "Name").flex(2.0).build(),
        column("department", "Department").flex(1.5).build(),
        column("salary", "Salary").fixed(100.0).align(Alignment::End).build(),
    ],
    &model.column_widths,
    &model.selection,
    &model.sort_order,
    // Row builder receives column widths for proper cell sizing
    |state, idx, is_selected, is_striped, widths| {
        let employee = &state.employees[idx];
        flex_row((
            // table_cell clips content to prevent overflow when columns are resized
            table_cell(label(employee.name.clone()).padding(4.0), widths[0]),
            table_cell(label(employee.department.clone()).padding(4.0), widths[1]),
            table_cell(label(format!("${:.0}", employee.salary)).padding(4.0), widths[2]),
        ))
        .background_color(if is_selected { BG_SELECTED } else { Color::TRANSPARENT })
    },
    |state, action| {
        match action {
            TableAction::Sort(col, dir) => state.sort_order = SortOrder::single(&col, dir),
            TableAction::Select(id, mods) => state.selection.select(id, mods),
            TableAction::Activate(id) => state.edit_employee(&id),
            TableAction::ColumnResized(key, width) => state.column_widths.set(&key, width),
        }
    },
)
```

## Compatibility

- **Compatibility**: Xilem main branch (git)
- **Platforms**: Tested on macOS Tahoe 26.3.1

## Just Commands

```bash
just build   # Build the library
just run     # Run the widget gallery
just doc     # Generate documentation
just test    # Run tests
just lint    # Run clippy
```

## Coding Style

I try to conform to SOLID and DRY.
- DRY = Don't Repeat Yourself. Try to reuse code.
- SOLID
    - S: Single Responsibility Principle
    - O: Open Closed Principle
    - L: Liskov Substitution Principle
    - I: Interface Segregation Principle
    - D: Dependency Inversion Principle

Also code smells should be avoided:
- Avoid files containing more than 1000 lines of code. These are almost impossible to read.
- Try to keep functions brief so that they fit entirely on one screen
- Try to avoid indentation and deep nesting. To me, clean code is code that looks as though it’s been neatly aligned to the left with a ruler.
- I know that complexity plays a key role in computer science. And of course, that’s the top priority. But I also want programmers to develop a feel for the CPU. Even on a small scale, when processing small amounts of data, you can still write efficient code. I hate waste. I started learning IT on a Commodore 16. I just can’t help myself. I always feel sorry for the CPU.
- Try to write tests as if they were a document. Tests are also a form of documentation. They should therefore be readable as such.
- Avoid god objects. Objects which contain everything. Stable code is distributed. If god objects appear then probably the "Single Responsibility Principle" was violated somewhere else.
- Delete dead code. We work with git. It can be revived later.
- Avoid signatures with long parameter lists

I refer to "Refactoring. Improving the Design of Existing Code. Second Edition",  Martin Fowler,  Kent Beck, 2018.

## Author

Jacek Wisniowski

## Attribution

Built on [Xilem](https://github.com/linebender/xilem) by the Linebender team.

## Licence

This crate is licensed under the Apache License 2.0.

### Rust Logo (Optional Feature)

Rust logo SVG icons are available via the `rust-logos` feature:

```toml
[dependencies]
xilem_extras = { version = "0.0.2", features = ["rust-logos"] }
```

This provides `rust_logo()`, `rust_gear()`, `rust_logo_complete()`, and `ferris()`.
The Rust logo and Ferris mascot are from [rust-lang/rust-artwork](https://github.com/rust-lang/rust-artwork) 
and are licensed under [CC-BY (Creative Commons Attribution)](https://creativecommons.org/licenses/by/4.0/). 
If you enable this feature, you must comply with CC-BY requirements.

This software is provided as-is, without warranty. Use at your own risk.

xilem_extras

xilem_extras Latest Version Download

Today's picks

Was this content helpful?

Recent Feedback

xilem_extras

xilem_extras Latest Version Download

Today's picks

Was this content helpful?

Recent Feedback

Download README