Chisle
The coding-agent plugin that bills 52% of a bare model across 20 live tasks. Terse persona + tool-output compressor + context diet.
翻訳待ち
Rust GUI components for building fantastic cross-platform desktop application by using GPUI.
翻訳待ち
Loading the full README. The saved excerpt is shown below.
Build fantastic, high-performance desktop apps with Rust and GPUI.
GPUI Kit is a comprehensive Rust desktop application framework. It combines a
production-ready UI system with application-grade data, layout, and editing
capabilities, all built on a reusable foundation of behavior, state, and
infrastructure. GPUI Kit ships 75+ documented components and primitives,
WebAssembly support, AccessKit accessibility, UI integration testing, and an
optional JavaScript extension runtime.Read the full README ↗Build fantastic, high-performance desktop apps with Rust and GPUI.
GPUI Kit is a comprehensive Rust desktop application framework. It combines a production-ready UI system with application-grade data, layout, and editing capabilities, all built on a reusable foundation of behavior, state, and infrastructure. GPUI Kit ships 75+ documented components and primitives, WebAssembly support, AccessKit accessibility, UI integration testing, and an optional JavaScript extension runtime.
Documentation: https://gpui-kit.com
gpui-kit The one crate applications depend on
├── gpui-base Unstyled behavior, state, and infrastructure
└── gpui-component GPUI Component: the complete styled UI system
gpui-kit pins the matching GPUI release and re-exports GPUI, base, component,
and assets, so a Rust application lists a single dependency. JavaScript extension
hosts add gpui-shell separately; its default components feature supplies the styled catalog.
See the executable application recipe and AI-assisted development acceptance checks for a tested starting point and verification commands.
wasm32-unknown-unknown.gpui-base.gpui-shell lets a shipped Rust host load panels and business logic as scripts, with every capability granted explicitly.Use gpui-component to keep the application coherent with one complete visual
and interaction system. Use gpui-base when your product needs to create and
own that system itself. Use gpui-shell when the application should be
extensible in JavaScript after it ships.
gpui-component | gpui-base | gpui-shell |
|---|---|---|
| Complete, styled components | Unstyled behavior and infrastructure | JavaScript runtime hosted by Rust |
| Productive defaults with theming | Full control over structure and visual design | Capabilities granted one at a time |
| Best for building applications | Best for building design systems | Best for plugins and scripted applications |
APPLICATION
│
┌───────────────────┼───────────────────┐
│ │ │
▼ ▼ ▼
┌──────────────────┐ ┌──────────────────┐ ┌──────────────────┐
│ gpui-component │ │ Your Design │ │ gpui-shell │
│ Styled UI │ │ System │ │ JS extensions │
└────────┬─────────┘ └────────┬─────────┘ └────────┬─────────┘
│ │ │
└────────────────────┼────────────────────┘
▼
┌──────────────────┐
│ gpui-base │
│ Behavior · State │
│ Infrastructure │
└────────┬─────────┘
▼
GPUI
Behavior belongs to the foundation. Presentation belongs to the application.
Use gpui-component when you want polished controls ready to ship. Build on
gpui-base when your application should own its component source, layout,
styling, and motion while reusing difficult interaction behavior. Add
gpui-shell when contributors should extend the product without a fork or
a release.
The layering follows the same separation that makes the shadcn ecosystem flexible:
This is the beginning of the README. Read the rest at the original. Read the full README ↗