unom/punktfunk
1
0
Fork 0
Code Issues Pull Requests Actions 13 Packages Projects Releases 32 Wiki Activity

feat(client/windows): make the console UI findable, and launchable on its own

Browse Source 
Two problems, one feature. The gamepad/couch UI existed but you had to
already know it was there:

- On the hosts page its card only rendered when a controller was CONNECTED,
  so with no pad plugged in there was no visible entry point at all -- the
  only other door being a per-host overflow menu behind a "..." nobody
  opens. The card now always shows, with copy that adapts to whether a pad
  is present, so the feature is findable before you own the hardware.
- There was no way to start it directly. An HTPC or TV box wants the couch
  interface as its first screen, not the desktop shell. "punktfunk-client
  --console" now hands straight off to it (fullscreen unless --windowed),
  which covers shortcuts, Steam entries, autostart and Task Scheduler.

The Start-menu tile needs its own executable: an MSIX <Application> cannot
pass arguments to a full-trust exe, so "punktfunk-client.exe --console" is
not expressible there. punktfunk-console.exe is a ~20-line hand-off to the
session binary's browse mode, staged into the package and given its own
tile ("Punktfunk Console").

Nothing new is implemented behind either door: a bare "--browse" was
already a complete standalone client (host list, discovery, PIN pairing,
settings, Wake-on-LAN, library). It just had no front door.

Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
This commit is contained in:
Enrico Bühler
2026-07-19 18:45:14 +02:00
parent aa45757a72
commit 2508b72062
7 changed files with 116 additions and 13 deletions
Download Patch File Download Diff File Expand all files Collapse all files
clients/windows/src/app/hosts.rs
+30 -10
View File
@@ -352,10 +352,15 @@ pub(crate) fn hosts_page(props: &HostsProps, cx: &mut RenderCx) -> Element {
);
}
// A controller is connected and a paired host is REACHABLE (advertising or probed —
// an offline host would just open the console onto an error scene): offer the couch
// experience — the console (gamepad) UI on the most recently used such host.
if CONSOLE_UI_AVAILABLE && props.pads > 0 {
// The couch entry point, for the most recently used paired + REACHABLE host (an offline
// one would just open the console onto an error scene).
//
// Deliberately NOT gated on a controller being connected any more: it used to be, which
// meant that with no pad plugged in the gamepad UI had no visible entry point on this
// page at all — its only other door is the per-host overflow menu, behind a "…" nobody
// opens. The card now always shows (the copy below adapts), so the feature is findable
// before you own the hardware for it.
if CONSOLE_UI_AVAILABLE {
let reachable = |k: &&crate::trust::KnownHost| {
hosts
.iter()
@@ -382,12 +387,27 @@ pub(crate) fn hosts_page(props: &HostsProps, cx: &mut RenderCx) -> Element {
card(
grid((
vstack((
text_block("Controller detected").font_size(14.0).semibold(),
text_block(format!(
"Browse {}\u{2019}s game library with the gamepad \u{2014} \
launches stream in the same window.",
k.name
))
text_block(if props.pads > 0 {
"Controller detected"
} else {
"Console UI"
})
.font_size(14.0)
.semibold(),
text_block(if props.pads > 0 {
format!(
"Browse {}\u{2019}s game library with the gamepad \u{2014} \
launches stream in the same window.",
k.name
)
} else {
format!(
"The couch interface for {} \u{2014} a controller- and \
remote-friendly library that launches streams in the same \
window. Works with keyboard arrows too.",
k.name
)
})
.font_size(12.0)
.wrap()
.foreground(ThemeRef::SecondaryText),