xavierk/voidkontrol
1
0
Fork 0
Code Issues 6 Pull Requests Actions Packages Projects Releases Wiki Activity

Establish a faithful IBM Carbon desktop UI strategy for Void Linux #4

New Issue
Closed
opened 2026-09-21 04:57:53 +00:00 by xavierk · 1 comment
xavierk commented 2026-09-21 04:57:53 +00:00
Owner
Copy Link
Copy Source

Question

Which UI strategy can faithfully follow IBM Carbon while running as a native-installable, unprivileged Wayland application on Void Linux? Verify official component support, tokens/themes, IBM Plex, keyboard navigation/accessibility, and relevant desktop wrapper/native-toolkit availability and limitations for glibc/musl. Compare a small number of realistic stacks and their lifecycle/dependency costs. Describe keyboard-layout, layer, macro, backup/restore and error-state interaction requirements. Do not build a mockup or select the final architecture; provide cited recommendations for the architecture decision.

Parent map: Find the way to VoidKontrol v1: complete verified Swarm75 control on Void Linux

## Question Which UI strategy can faithfully follow IBM Carbon while running as a native-installable, unprivileged Wayland application on Void Linux? Verify official component support, tokens/themes, IBM Plex, keyboard navigation/accessibility, and relevant desktop wrapper/native-toolkit availability and limitations for glibc/musl. Compare a small number of realistic stacks and their lifecycle/dependency costs. Describe keyboard-layout, layer, macro, backup/restore and error-state interaction requirements. Do not build a mockup or select the final architecture; provide cited recommendations for the architecture decision. Parent map: [Find the way to VoidKontrol v1: complete verified Swarm75 control on Void Linux](https://git.bongbetic.com/xavierk/voidkontrol/issues/1)
xavierk added the wayfinder:researchwayfinder:child-of-1 labels 2026-09-21 04:57:53 +00:00
xavierk self-assigned this 2026-09-21 04:59:06 +00:00
xavierk commented 2026-09-21 05:07:25 +00:00
Author
Owner
Copy Link
Copy Source

Resolution

Official Carbon React and Web Components are maintained first-party implementations; Qt/QML would require a custom Carbon implementation. Recommend evaluating Carbon React in an unprivileged Tauri application first, using Void's GTK3/WebKitGTK 4.1 packages. This is a candidate, not an architecture decision or a tested application.

The inspected Void Electron template is marked broken, while Tauri's upstream Alpine guidance and Void WebKit package source show that musl cannot simply be ruled out; target-specific builds and native Wayland/accessibility tests remain required. The report specifies theme/font/license obligations, keyboard-accessible editing, pending versus verified state, and safe error/restore interactions.

IBM Carbon desktop UI strategy report contains the cited evidence and proof gates, captured on research/carbon-ui.

This resolves the research question. Wrapper selection, target libc/architecture, theme policy, and interaction approval remain in Choose the VoidKontrol service, UI, and desktop integration architecture and its downstream decisions. No application or hardware control was implemented.

## Resolution Official Carbon React and Web Components are maintained first-party implementations; Qt/QML would require a custom Carbon implementation. Recommend evaluating Carbon React in an unprivileged Tauri application first, using Void's GTK3/WebKitGTK 4.1 packages. This is a candidate, not an architecture decision or a tested application. The inspected Void Electron template is marked broken, while Tauri's upstream Alpine guidance and Void WebKit package source show that musl cannot simply be ruled out; target-specific builds and native Wayland/accessibility tests remain required. The report specifies theme/font/license obligations, keyboard-accessible editing, pending versus verified state, and safe error/restore interactions. [IBM Carbon desktop UI strategy report](https://git.bongbetic.com/xavierk/voidkontrol/src/commit/49162afefd453710b7e1f1f18f9bcd94eca008df/docs/research/carbon-ui.md) contains the cited evidence and proof gates, captured on `research/carbon-ui`. This resolves the research question. Wrapper selection, target libc/architecture, theme policy, and interaction approval remain in [Choose the VoidKontrol service, UI, and desktop integration architecture](https://git.bongbetic.com/xavierk/voidkontrol/issues/6) and its downstream decisions. No application or hardware control was implemented.
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels
wayfinder:child-of-1
Child of the VoidKontrol v1 decision map
 wayfinder:grilling
Decision requiring a live exchange with the user
 wayfinder:map
Canonical wayfinding decision map
 wayfinder:prototype
Decision supported by a user-reviewed prototype
 wayfinder:research
Primary-source investigation for a decision
 wayfinder:task
Prerequisite work that unblocks a decision
No labels wayfinder:child-of-1 wayfinder:research
Milestone
No items
No Milestone
Projects
Clear projects
No projects
Assignees
Clear assignees
xavierk (Xavier Karma)
No Assignees xavierk
1 Participants
Notifications
Due Date
No due date set.
Blocks
#6 Choose the VoidKontrol service, UI, and desktop integration architecture
xavierk/voidkontrol
Reference: xavierk/voidkontrol#4