Panels: close, back, placement, the Settings link and widths differ from panel to panel

未关闭
#166 0 条评论 0 个 reaction 已指派 0 人 在 GitHub 查看

维护者通常 1 天内回复

还没有人认领这个 Issue。

评估

难度
4/5
预计耗时
3-5 天
新手友好度
58/100
Issue 类型
重构
描述清晰度
基本清楚
活跃度
活跃
领域
desktop

调研方向

Read the panels in quickshell/.config/quickshell/desktop/panels/*.qml and shared components in quickshell/.config/quickshell/desktop/components/; compare their headers, placement, Settings links, and widths. Check how panels are opened through desktop-shell toggle and from Control Center, since routes may differ. Done means panels share a consistent header and Settings action, use a small set of widths, and preserve appropriate back and close controls.

由索引模型根据 Issue 内容生成。

描述

area: shell enhancement

Today

  • Close: an X at the top right (most panels), a Chiudi text button at the bottom right (Hints, Calendar, Audio, Wallpaper picker), a centred Chiudi (Power menu), nothing (Launcher, Settings).
  • Back: an arrow at the top left (Network, Bluetooth), a ← Centro di controllo link at the bottom left (Audio).
  • Placement: Network, Bluetooth and Battery open as side sheets under the bar; Audio and Displays open as centred dialogs. (Opened through desktop-shell toggle; the route from the Control Center may differ.)
  • Settings link: Impostazioni… floats alone at the bottom right of the Control Center, Network, Bluetooth, Agent, Updates and Displays.
  • Widths: about ten different panel widths between 440 and 1240.

Proposal

One shared panel header (back, title, actions, close) used by every panel, the Settings link as a header action, and a small set of panel widths.

Where

quickshell/.config/quickshell/desktop/panels/*.qml, quickshell/.config/quickshell/desktop/components/.


From the shell UI review of 2026-11-11, finding A4. Seen on a 1920×1080 external monitor at scale 1, locale it_IT, theme Dynamic, bar style Transparent. Italian labels are quoted as they appear on screen.

主要语言
QML
星标
3
派生
0
平均合并
48 分钟
30 天内合并 PR
99

环境准备

这个项目没有提供开发容器、Dockerfile 或贡献指南,环境需要你自己搭建:先看它的 README,通用步骤见我们的新手贡献指南。

从这里开始

  1. 先读完整个 Issue,再读项目的贡献指南。
  2. 在 Issue 下留言说明你要接手 —— 这能避免两个人做同样的事。
  3. Fork 仓库,在一个分支上完成修改。
  4. 提交 Pull Request,并在描述里引用这个 Issue 编号。

angelobdev/dotfiles 的其他 Issue

查看 angelobdev/dotfiles 的全部 Issue

相似的 Issue

更多 Desktop Dev Issue

把新 issue 发到你的邮箱

精选适合新手参与的 GitHub issue 摘要。