Re: [Ayatana] Merging libindicate into libnotify

[Conscious User <conscioususer@xxxxxxx>]

> The idea that all non-immediate "notifications" should be grouped
> together in a single place, regardless of topic, is very much like the
> idea that progress for all long-running tasks should be grouped
> together in a single place regardless of task. It's the kind of
> categorization that may make perfect sense to engineers, but to others
> it risks looking like a jumble of unrelated things.

What are your thoughts on, for example, what Jockey, PolicyKit and File
Transfer currently do? They basically use an appindicator to persist,
just like Update Manager did in the past with the notification area.

Do you think this should be the standard procedure for all apps that
do not fit in the current categories (messaging and sound)?

If no, how should they be fixed? If yes, why not do something similar
for Update Manager instead of popping up the window?

> One of the motivations behind the introduction of Notify OSD was
> to encourage applications to use general-purpose notification systems
> less often. Notifications of things are more helpful if they are
> closer to those things, for example embedded in relevant windows.

Aren't the most common usage of notifications the situations where
relevant windows are *not* currently in sight, or when there is no
such thing as "relevant windows" at all?