oneo-me/onevra

English | 简体中文

Onevra is a Go component library for native desktop applications, built on MyGo. It provides themed controls, window shells, Lucide icons and complex components. The name combines One from ONEO with the coined ending vra.

Onevra builds on MyGo rather than replacing it:

• Refine built-in components: adjust the styling of MyGo's built-in components, and merge and simplify them into a smaller, consistent API.
• Fill the gaps: provide components that MyGo does not officially support.
• Defer to upstream: when MyGo officially provides a feature or component that Onevra already offers, Onevra may remove its own version and switch to MyGo's.

Building on MyGo's native UI capabilities, Onevra adds composed components for common application scenarios:

• Conversation interfaces: bring message turns, tool activity, folded summaries and attachment input together into a complete chat interface.

• Lucide icons: provide SVG icons for MyGo through named accessors, loaded on demand with configurable sizing and inherited text color.

Follow MyGo’s official requirements for the development environment and system dependencies.

From the repository root, start the interactive Gallery:

cd source
go run ./examples/gallery

Append -theme light or -theme dark to preview an appearance. Five smaller applications are also available; run these commands from source/:

Each template includes localization and its own packaging configuration; all but the document editor and the game keep preferences. See starter applications for copying and adapting one. Windows and Linux still require their own native review.

Install 0.2026.12 in your application module with:

go get github.com/oneo-me/onevra/source@v0.2026.12

Save this minimal application as main.go and run go run . from your application module:

package main

import (
    "log"

    "github.com/egoist/mygo"
    "github.com/egoist/mygo/ui"
    "github.com/oneo-me/onevra/source/components"
    "github.com/oneo-me/onevra/source/shells/plain"
    "github.com/oneo-me/onevra/source/theme"
)

func main() {
    mygo.App.WhenReady(func() {
        shell := plain.NewShell(plain.ShellOptions{
            Title: "Hello Onevra",
            Theme: theme.Onevra,
            Content: func(c *ui.Context) {
                ui.Column(c).Fill().Padding(24).Children(func() {
                    components.Text(c, "Hello, Onevra!")
                })
            },
        })
        shell.Window().OnClosed(func() { mygo.App.Quit() })
    })
    if err := mygo.App.Run(); err != nil {
        log.Fatal(err)
    }
}

Create windows after MyGo is ready. Build content with Onevra controls and MyGo layout primitives; your application owns state, persistence and asynchronous work.

Package applications with MyGo's own CLI; Onevra adds no packager. To run or package Gallery, execute these commands from source/:

go tool mygo dev
go tool mygo build

dev builds and launches the host application with live reload; build packages it for the host, or for the targets given with -platform. Configuration lives in mygo.json. See packaging the Gallery and MyGo's distribution guide.

Shells create native windows while leaving application lifecycle, business state and the theme to the caller.

Import either package under github.com/oneo-me/onevra/source/. Their Theme option installs the application's theme before each frame: pass theme.Onevra for Onevra's palettes, your own function returning a *ui.Theme, or nothing to keep MyGo's theme. Choose light, dark or system appearance with mygo.Theme.SetSource; see the theme package. For Sidebar, use sidebar.HeaderHeight(c) when content needs to clear the floating header; see layout guidance.

The Lucide package provides named SVG accessors. Import github.com/oneo-me/onevra/source/icons/lucide alongside components, then use them in a content builder:

components.Icon(c, lucide.Search).Size(20, 20)

Icons are parsed on first use and reused. They inherit text color, and the Icon component also accepts a parsed MyGo SVG.

Import github.com/oneo-me/onevra/source/components for themed inputs, selection, navigation, collections and overlays. Inside a content builder, use retained application state such as agreed and wifi:

if components.Button(c, "Save", components.ButtonPrimary).Clicked() {
    // Save application state.
}
components.Checkbox(c, &agreed, "I agree")
components.Switch(c, &wifi, "Wi-Fi")

Components read the frame theme and work independently of Shell; a standalone window installs its theme with c.SetTheme or theme.Apply at the top of its builder. See the component contract and theme usage. Complex components each have a separate package under components/: chart, graph, treemap, flow, gesture, command and chat. See complex component composition.

Read AGENTS.md and the architecture overview before making changes. From source/, run:

gofmt -l .
GOWORK=off go test ./...
GOWORK=off go test -race ./...
GOWORK=off go vet ./...
GOWORK=off go build ./...

Formatting should produce no output. See development checks and native review for verification. Keep both READMEs equivalent and record consumer-visible changes in CHANGELOG.md. Versioning and release procedures are in Publication.

The marketing site lives in website/ and is built with React Router and shadcn/ui. Its /components page runs the Gallery's demonstrations in the browser as WebAssembly, covering every Onevra component page. The Website workflow deploys it to GitHub Pages.

Go 1.27.1 or later is also required to compile the browser previews.

cd website
bun install
bun run dev

See website/README.md for the build and deployment details.

Project code: MIT. Components adapted from MyGo retain the upstream MIT notice. Lucide assets retain their upstream ISC and Feather MIT notices.