# GPUI Component — Rust GUI Kit

> desc

## Install

Save as a script file and run:

# GPUI Component

## Quick Use
```toml
[dependencies]
gpui_component = { git = "https://github.com/longbridge/gpui-component" }
```

## Introduction
GPUI Component provides a comprehensive set of pre-built UI widgets for the GPUI rendering framework. It brings production-ready buttons, inputs, tables, modals, and more to Rust desktop development.

## What GPUI Component Does
- Provides 40+ ready-to-use UI components (buttons, inputs, dropdowns, tables, modals)
- Renders at native speed using GPU-accelerated drawing via GPUI
- Supports light and dark themes with a flexible theming system
- Handles keyboard navigation and focus management
- Works on macOS, Linux, and Windows

## Architecture Overview
GPUI Component is a pure-Rust library built on GPUI, a GPU-accelerated UI framework originally created for the Zed editor. Each component is a composable Rust struct implementing GPUI view traits. The theming layer uses a token-based design system where colors, spacing, and typography are centralized.

## Self-Hosting & Configuration
- Add the crate as a Git dependency in Cargo.toml
- Requires Rust nightly and platform-specific GPUI prerequisites
- Themes are configured by providing a custom ThemeColors struct
- Components accept builder-pattern configuration
- Example apps in the repository demonstrate usage patterns

## Key Features
- GPU-accelerated rendering for smooth 120fps interfaces
- Comprehensive component library for desktop UI patterns
- Token-based theming with built-in light and dark modes
- Composable architecture for custom components
- Active development aligned with the GPUI framework

## Comparison with Similar Tools
- **egui** — Immediate-mode and browser-portable; GPUI Component is retained-mode with richer design
- **Iced** — Elm architecture; GPUI Component uses a view-model pattern closer to native toolkits
- **Dioxus** — Targets web and desktop via HTML-like syntax; GPUI Component renders directly to GPU
- **GTK/Qt bindings** — Mature ecosystems but require FFI; GPUI Component is pure Rust

## FAQ
**Q: Is GPUI the same framework used by Zed?**
A: Yes. GPUI was created for the Zed code editor.

**Q: Does it work on Windows?**
A: Yes, though macOS has the most mature support.

**Q: Can I use it for web applications?**
A: No. GPUI Component targets native desktop only.

**Q: How stable is the API?**
A: Evolving alongside GPUI. Expect breaking changes before 1.0.

## Sources
- https://github.com/longbridge/gpui-component
- https://gpui.rs

---
Source: https://tokrepo.com/en/workflows/asset-559a1515
Author: Script Depot