Show the Store as cards led by each widget's screenshot
I maintainer di solito rispondono entro 1 giorno
Nessuno ha ancora preso questa issue.
Valutazione
- Difficoltà
- 4/5
- Tempo stimato
- 3-5 giorni
- Idoneità per principianti
- 52/100
Direzione di ricerca
Start with Sources/StableBar/PackagesView.swift, especially the widget and theme rows at lines 362–365, and read the existing StoreCard implementation from the related #235/#236 work. Compare the current category sections and package preview loading with the proposal’s card states, sample widget content, adaptive columns, and keyboard behavior. Done means Store packages, themes, included widgets, and packages without screenshots render the specified card content and actions, with keyboard activation and two or three columns as the pane width changes.
Scritto dal modello di indicizzazione a partire dal testo della issue.
Descrizione
Problem
A widget package's row in Settings → Store shows only an SF Symbol. To see what the widget puts on the bar, you open its page, which shows the author's screenshot. Theme rows already show a small preview of each theme, so you can compare themes as you scroll. You can't do that with widgets.
The symbol says what a widget is about, not what it shows. Status ring's gauge doesn't show its ring and Wi-Fi glyph, AI usage's gauge hides two pairs of bars with percentages, and Dock badges' symbol doesn't show the app icons with their counts. For simple widgets, such as GitHub notifications (a bell and a count), the symbol is already close to what the bar shows.
Proposal
Show the Store as cards again, each led by what the widget looks like, keeping #711's sidebar, sources and category sections. Every Store widget package now has a screenshot: stablebar-packages CI requires a 520 × 144 PNG with the widget centered on a plain background, and the index lists its URL. #236's cards showed these screenshots too. #711 replaced the cards because of how they were ordered and grouped (by install state, with no categories), not because of the cards themselves. Cards inside category sections haven't been tried.
The attached renders use the current Store screenshots in a dark Settings window.
Each card has:
- A banner, the full width of the card at the screenshot's 520 × 144 proportions. At three columns the widget shows at about its size on the bar, so the author's image needs no cropping.
- A Store or private package shows its screenshot, loaded from the index's
screenshotURL asPackageListPreviewdoes, without downloading the package. - A theme shows its drawn preview, as its row does today.
- An included widget has no screenshot. It is drawn with sample data (
WidgetSampleContent), which matches the bar because included widgets use the built-in layouts. - A package without a screenshot, from a private source or a local folder, shows its symbol in the banner.
- A Store or private package shows its screenshot, loaded from the index's
- The symbol and the full name on one line. The symbol stays the package's icon everywhere (#818).
- Two lines of description, with the rest on hover.
- The action at the bottom: Get, Update, Add to bar, Use, or the installed state with its ⋯ menu.
Columns adapt to the pane: three at the default Settings size, two at its minimum width. Cards should take keyboard focus and open with Return or Space, which #236's cards didn't.
For density, three columns cost about 56 pt per package against 48 pt per row today. Sections with one card leave the rest of their row empty. That's rare in practice, because included widgets share the categories: Apps & windows and System each hold eight items.
Alternatives:
- The row, plus the widget at bar size. The screenshot, cropped to the widget by its plain background, sits beside Get. This keeps #711's rows, but it needs a crop that can fail, and wide widgets shorten the description line.
- The whole screenshot as the row's thumbnail, as theme rows do today (72 × 36 pt). The widget fills a small part of the image, so it shrinks to a few points and can't be read.
Every screenshot is drawn in Light mode, so cards in a dark Settings window have light banners. #819 covers previews for the dark appearance, which matters more once every card shows one.
Possible today
No. Widget rows draw RowIcon(symbol: entry.symbol ?? "shippingbox") (Sources/StableBar/PackagesView.swift:365), and only theme rows get PackageListPreview (:362). Checked on origin/main at da7455a and on stablebar-packages main.
Related
- #235 / #236 made the Store a grid of cards (
StoreCard, 0c5c7ee) with each package's preview. #711 replaced the grid with one list of rows for included widgets, Store packages and themes, grouped by category. - #144 / #152 put previews in the package list.
- #818: the package page's icon should match the card's.
- #819: previews for a dark Settings window.
Triaged by Claude Code (Claude Opus 5.5).
- Lingua principale
- Swift
- Stelle
- 184
- Fork
- 12
- Merge medio
- 3h 50m
- PR unite (30g)
- 387
Preparare l'ambiente
- Nessun Dockerfile né file Docker Compose
- Ha un modello di pull request
- Leggi la guida per i contributori
Come iniziare
- Leggi tutta la issue e poi la guida ai contributi del progetto.
- Commenta sulla issue per dire che te ne occupi tu — evita che due persone facciano lo stesso lavoro.
- Fai un fork del repository e lavora su un branch.
- Apri una pull request che faccia riferimento al numero della issue.
Altre issue di Seb-GRAF/StableBar
-
enhancement
Difficoltà 2/5 1-3 ore Idoneità per principianti 82/100
I maintainer di solito rispondono entro 1 giorno
-
Menu bar items drawn as in the menu bar show the wrong part of the menu bar after a display changeForse già presa @Jonathanm10 l’ha presa oggi. Apertaneeds-triage
Difficoltà 2/5 1-3 ore Idoneità per principianti 35/100
I maintainer di solito rispondono entro 1 giorno
-
enhancement
Difficoltà 5/5 Più di una settimana Idoneità per principianti 30/100
I maintainer di solito rispondono entro 1 giorno
-
Allow the App Menu to display the frontmost app iconForse già presa @khatami10 l’ha presa oggi. Apertaenhancement needs-triage
Difficoltà 3/5 1-2 giorni Idoneità per principianti 35/100
I maintainer di solito rispondono entro 1 giorno
-
bug
Difficoltà 4/5 3-5 giorni Idoneità per principianti 54/100
I maintainer di solito rispondono entro 1 giorno
Tutte le issue di Seb-GRAF/StableBar
Issue simili
-
good first issue help wanted testing
Difficoltà 1/5 Meno di un'ora Idoneità per principianti 78/100
-
area:cli documentation good first issue priority:low
Difficoltà 1/5 Meno di un'ora Idoneità per principianti 94/100
isaaclins/freesnitch#430 ·
I maintainer di solito rispondono entro 1 giorno
-
bug
Difficoltà 2/5 1-3 ore Idoneità per principianti 82/100
MasterJ93/ATProtoKit#354 ·
-
enhancement help wanted
Difficoltà 2/5 1-3 ore Idoneità per principianti 84/100
heysidhant/appvanish#4 ·
-
bug priority:low status:queued
Difficoltà 2/5 1-3 ore Idoneità per principianti 82/100
I maintainer di solito rispondono entro 1 giorno