Add a standard AdwAboutDialog wired to app metadata, plus the AppStream metainfo file it should share data with. Use when adding an About entry, release notes, credits, or preparing app metadata.
中文简介正在准备中。当前显示原文说明。
查看安装方法安装前可以查看交给 AI 代理的指令内容。
Every GNOME app has an "About <App>" item last in its primary menu, opening an
AdwAboutDialog.
menu primary_menu {
section {
item { label: _("_About My App"); action: "app.about"; }
}
}
Label is "About <full app name>", always the last item, no ….
If the app ships AppStream metainfo (it should), let libadwaita read it — release notes, developer, website all come from one place:
def _on_about(self, action, param):
about = Adw.AboutDialog.new_from_appdata(
'/org/example/MyApp/org.example.MyApp.metainfo.xml', '1.2.0')
about.set_copyright('© 2026 Developer')
about.present(self.props.active_window)
(Requires the metainfo XML in gresources.) Rust:
adw::AboutDialog::from_appdata(path, Some("1.2.0")).
about = Adw.AboutDialog(
application_name='My App',
application_icon='org.example.MyApp', # = app ID
version='1.2.0',
developer_name='Jane Developer', # person or team, not company boilerplate
developers=['Jane Developer', 'Sam Contributor'],
designers=['Alex Designer'],
translator_credits=_('translator-credits'), # translated by each locale
license_type=Gtk.License.GPL_3_0,
website='https://example.org/myapp',
issue_url='https://github.com/example/myapp/issues',
)
about.add_link(_("_Documentation"), "https://example.org/docs")
about.present(self.props.active_window)
<?xml version="1.0" encoding="UTF-8"?>
<component type="desktop-application">
<id>org.example.MyApp</id>
<metadata_license>CC0-1.0</metadata_license>
<project_license>GPL-3.0-or-later</project_license>
<name>My App</name>
<summary>Do one thing well</summary>
<description><p>Longer description for software centers.</p></description>
<developer id="org.example"><name>Jane Developer</name></developer>
<url type="homepage">https://example.org/myapp</url>
<url type="bugtracker">https://github.com/example/myapp/issues</url>
<launchable type="desktop-id">org.example.MyApp.desktop</launchable>
<content_rating type="oars-1.1"/>
<releases>
<release version="1.2.0" date="2026-07-19">
<description><p>What changed, user-facing wording.</p></description>
</release>
</releases>
</component>
Validate: appstreamcli validate data/*.metainfo.xml.in
application_icon = app IDmeson.project_version()issue_url set (gives the dialog a Report an Issue row)Related: skills/flatpak-packaging/SKILL.md (metainfo is required for Flathub).
还没有评价。欢迎分享你的使用感受。
无需登录即可发表。欢迎分享使用感受、提问，或说明在哪些环境下无法运行。
还没有评论。来写第一条吧。
Make a GTK4/libadwaita app accessible — accessible labels and roles, tooltips on icon-only buttons, keyboard navigation, contrast, and testing with Orca/Accerciser. Use when fixing a11y issues or running the accessibility category of a HIG audit.
中文简介正在准备中。当前显示原文说明。
Responsive GNOME layouts: AdwBreakpoint conditions, BreakpointBin, MultiLayoutView, BottomSheet, narrow/wide layout swaps. Use when making an app work on phones or narrow windows.
中文简介正在准备中。当前显示原文说明。
Onboarding tour with AdwCarousel and navigation dots, skippable welcome screens. Use when adding a first-run tour or feature showcase to a GNOME app.
中文简介正在准备中。当前显示原文说明。
Implement GNOME's 4-tier destructive-action pattern: undo toasts instead of confirmation dialogs, AdwAlertDialog for irreversible actions. Use when adding delete, remove, clear, or other destructive actions.
中文简介正在准备中。当前显示原文说明。
Loading, empty, and error states with AdwStatusPage and AdwSpinner — placeholder icons, titles, action buttons. Use when an app view can be empty, loading, or failed.
中文简介正在准备中。当前显示原文说明。
Package a GNOME app as a Flatpak — manifest for the GNOME runtime, sandbox permissions, build/run/test loop, and Flathub submission checklist. Use when packaging, distributing, or preparing a GNOME app for Flathub.
中文简介正在准备中。当前显示原文说明。