Module notify 

User notifications: tilo_notify under the toolkit’s module path.

Modules

conformance

The contract every Notifier keeps, as checks a backend’s tests (and a host’s own backend’s tests) run, plus a Recording notifier.

Structs

AlarmSchedule

A calendar handoff together with this device’s delivered occurrence. Carrying the local date keeps host recomputation from rearming it.

AlarmState

The host’s authoritative occurrence and delivery history for an alarm.

CalendarAlarm

An alarm in this device’s local time. Monday is bit zero; no weekdays means a single occurrence. A repeating alarm needs no network connection.

Notification

One user-visible notification.

NotificationButton

A button on a notification.

PriorityContact

A person whose messages may break through Do Not Disturb.

Scheduled

A notification the platform holds for later delivery.

SystemTime

A measurement of the system clock, useful for talking to external entities like the file system or other processes.

Enums

Availability

Whether a feature can be used on a target.

CloseReason

Why the platform closed a notification the app showed, before the app took it back itself, as org.freedesktop.Notifications’ NotificationClosed names it.

Feature

One capability of this crate, for availability and Unsupported.

NotifyError

Why a notification could not be shown, scheduled or withdrawn.

Severity

How much a notification asks of the person.

Constants

MAX_BUTTONS

The most buttons a notification carries, as the Tilo shell shows them.

Traits

Notifier

Host-owned user notifications.

Functions

availability

Whether feature can be used on this target.

available

Whether feature can be used on this target without a prompt.

publish_priority_contacts

Replace the people whose notifications break through Do Not Disturb with contacts. Only the Tilo shell takes such a list, and only from an app it launched as app_id (Feature::PriorityContacts). Blocks on the session bus: call it off the UI thread.

report_activation

Report that the person chose a notification carrying uri, for a host that shows applications’ notifications itself (a desktop drawing its own banners) rather than through a platform backend. The app’s set_activation_handler receives it as it would a platform click.

set_activation_handler

Call handler with the activation URI of every notification the user clicks whose URI has scheme (tilo-clocks), on whatever thread the platform reports it, starting with any such click that arrived before (the one that launched the app). Replaces an earlier handler for scheme.

set_close_handler

Call handler with the tag and reason of every notification whose tag starts with prefix that the platform closes, on whatever thread reports it. Replaces an earlier handler for prefix; where prefixes nest, the longest one wins.

system

This target’s notifications for the app app_id. A desktop attributes notifications to an app, so without an id (a tool, a test, the shell) they are unavailable there; a browser attributes them to the page’s origin and needs none.

unavailable

Notifications that are never shown, for hosts that offer none.

valid_activation

scheme:rest, the scheme as RFC 3986 spells it, without control characters or whitespace.

Type Aliases

Unsupported

A feature this target, or this particular host, cannot provide.