Re: [Ayatana] Merging libindicate into libnotify

2011-04-05 Thread Matthew Paul Thomas
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Conscious User wrote on 01/04/11 18:57: 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

Re: [Ayatana] Merging libindicate into libnotify

2011-04-01 Thread Matthew Paul Thomas
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Conscious User wrote on 31/03/11 18:57: ... In Natty, the Ubuntu One item was moved from the Me Menu from the Messaging Menu. Was this agreed on by the design team? Not as far as I know. I reported a bug about it that was marked Invalid.

Re: [Ayatana] Merging libindicate into libnotify

2011-04-01 Thread Conscious User
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

Re: [Ayatana] Merging libindicate into libnotify

2011-03-31 Thread Dylan McCall
The existence of libindicate is something that has always bothered me. The not-necessarily-immediate-response case is a common scenario required by a significative number of applications, and requiring those applications to support an extra library (and thus extra patching for working in

Re: [Ayatana] Merging libindicate into libnotify

2011-03-31 Thread Conscious User
Le jeudi 31 mars 2011 à 12:35 -0700, Dylan McCall a écrit : This is something that _is_ covered by a particular subset of the notification specification; it's just that it isn't guaranteed. Gnome Shell is doing what you want here: they went ahead and defined persistent notifications, which