Skip to content
cccskills
FreePublished on GitHub

gnome-toast-feedback

In-app notifications: AdwToast/ToastOverlay with undo buttons, when to use toasts vs banners vs dialogs. Use when giving feedback after user actions in a GNOME app.

The English summary is being prepared. Showing the original description.

See how to install

Files included (1)

  • SKILL.md3.0 KB

SKILL.md (original)

Review the instructions the agent will receive before you install.

Skill: Toast Notifications & Feedback

Goal: Show transient feedback with optional undo actions.

Setup: Wrap Everything in ToastOverlay

<object class="AdwToastOverlay" id="toast_overlay">
  <property name="child">
    <!-- ALL window content goes here -->
  </property>
</object>

Wrap the entire window content, not individual sections.

Simple Toast

Python:

self.toast_overlay.add_toast(Adw.Toast.new("File saved."))

Rust:

let toast = adw::Toast::new("File saved.");
self.imp().toast_overlay.add_toast(toast);

C:

adw_toast_overlay_add_toast (overlay, adw_toast_new (_("File saved.")));

Toast with Undo Button

Python:

toast = Adw.Toast.new(f"Deleted {filename}")
toast.set_button_label("Undo")
toast.set_priority(Adw.ToastPriority.HIGH)
toast.connect("button-clicked", lambda t, filename=filename: undo_delete(filename))
toast_overlay.add_toast(toast)

Rust (Loupe pattern):

let toast = adw::Toast::builder()
    .title(gettext("Image moved to trash"))
    .button_label(gettext("Undo"))
    .priority(adw::ToastPriority::High)
    .build();
toast.connect_button_clicked(glib::clone!(#[strong] file, move |_| {
    restore_from_trash(&file);
}));
self.imp().toast_overlay.add_toast(toast);

C:

AdwToast *toast = adw_toast_new_format (_("Deleted \"%s\""), filename);
adw_toast_set_button_label (toast, _("_Undo"));
adw_toast_set_action_name (toast, "app.undo");
adw_toast_set_priority (toast, ADW_TOAST_PRIORITY_HIGH);
adw_toast_overlay_add_toast (overlay, toast);

Priority Levels

PriorityUse
NORMALRoutine feedback ("File saved", "Copied")
HIGHImportant feedback, undo actions ("Deleted", "Trashed")

When to Use Toast vs Banner vs Dialog

PatternWidgetUse Case
ToastAdwToastTransient event feedback, undo actions
BannerAdwBannerPersistent state (offline, syncing, read-only)
DialogAdwDialogComplex input, blocking choices
Status PageAdwStatusPageEmpty/error states

Toast Rules

  • Short title (1-5 words)
  • Button only if directly relevant (Undo, Retry)
  • Position: bottom-center of window (automatic)
  • Auto-dismisses after a few seconds (HIGH priority stays longer)
  • Do NOT show toasts for errors that need user action — use banners

Banner Example (persistent state)

<object class="Adw.Banner">
  <property name="title" translatable="yes">Offline</property>
  <property name="button-label" translatable="yes">_Retry</property>
</object>

Real App References

  • Loupe: trash + undo toast (src/widgets/image_window.rs)
  • Clocks, Loupe: ToastOverlay wrapping whole content
  • gnome-calendar: Banner for read-only calendar

Reviews

No reviews yet. Tell others what you thought.

Comments

No login needed. Share how it worked for you, ask a question, or note where it did not run.

No comments yet. Be the first to write one.

Comments are published right away. Do not include personal information such as email addresses or phone numbers. Up to 2 URLs.

0 / 1,000 characters

This form is protected by reCAPTCHA, and the Google Privacy Policy and Terms of Service apply.

More skills from this repository

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.

The English summary is being prepared. Showing the original description.

hanthor/gnome-gui-spec4Updated Oct 11, 2026

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.

The English summary is being prepared. Showing the original description.

hanthor/gnome-gui-spec4Updated Oct 11, 2026

Responsive GNOME layouts: AdwBreakpoint conditions, BreakpointBin, MultiLayoutView, BottomSheet, narrow/wide layout swaps. Use when making an app work on phones or narrow windows.

The English summary is being prepared. Showing the original description.

hanthor/gnome-gui-spec4Updated Oct 11, 2026

Onboarding tour with AdwCarousel and navigation dots, skippable welcome screens. Use when adding a first-run tour or feature showcase to a GNOME app.

The English summary is being prepared. Showing the original description.

hanthor/gnome-gui-spec4Updated Oct 11, 2026

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.

The English summary is being prepared. Showing the original description.

hanthor/gnome-gui-spec4Updated Oct 11, 2026

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.

The English summary is being prepared. Showing the original description.

hanthor/gnome-gui-spec4Updated Oct 11, 2026

See all skills by hanthor

Report a problem with this skill