Re: new module proposal: notification-daemon+libnotify
Hi Christian! The tentative plan for notification-daemon and libnotify is to move them into SVN and switch over to Bugzilla. I'm then hoping to get someone to act as a co-maintainer for this. There will be a formal code review process for these modules, using a Review Board installation I'm setting up. All code will be expected to go through this before being committed in the code base (aside from translations). How is this plan going? Cheers, Frederic ___ desktop-devel-list mailing list desktop-devel-list@gnome.org http://mail.gnome.org/mailman/listinfo/desktop-devel-list
Re: new module proposal: notification-daemon+libnotify
No progress yet. Been too busy with work-related things and the holidays. Christian -- Christian Hammond - [EMAIL PROTECTED] VMware, Inc. On Thu, Dec 4, 2008 at 5:56 AM, Frederic Peters [EMAIL PROTECTED] wrote: Hi Christian! The tentative plan for notification-daemon and libnotify is to move them into SVN and switch over to Bugzilla. I'm then hoping to get someone to act as a co-maintainer for this. There will be a formal code review process for these modules, using a Review Board installation I'm setting up. All code will be expected to go through this before being committed in the code base (aside from translations). How is this plan going? Cheers, Frederic ___ desktop-devel-list mailing list desktop-devel-list@gnome.org http://mail.gnome.org/mailman/listinfo/desktop-devel-list
Re: new module proposal: notification-daemon+libnotify
On Sun, 2008-11-16 at 02:35 +0200, natan yellin wrote: Where is the code currently hosted? Subdirs of http://svn.galago-project.org/trunk/ Nicolas I'd like to play around with this if I have time. -Natan 2008/11/6 Christian Hammond [EMAIL PROTECTED] I can assure you that this hasn't bit-rotted. It has been in development, but my work on Unity at VMware this past year basically took up all my free time. I would be happy to have people who want to contribute and fix bugs. I plan to keep the roll as maintainer, and have a couple people in mind for a co-maintainer. If people really want certain things in or fixed, by all means, submit patches. Nobody has done so in a while and nobody's really been complaining about anything to my knowledge, so I haven't felt that a release was that urgent. Still, there are some important fixes in SVN, some of which were waiting for additional patches that I never got and only recently had time to finish up. I should be in a good position to do a release soon. Christian -- Christian Hammond - [EMAIL PROTECTED] VMware, Inc. On Thu, Nov 6, 2008 at 8:46 AM, Patryk Zawadzki [EMAIL PROTECTED] wrote: On Thu, Nov 6, 2008 at 5:30 PM, A. Walton [EMAIL PROTECTED] wrote: There are other maintenance-related issues to bring up as well, like the duplicated functionality in having both notification-daemon+libnotify and libcanberra doing sound notifications (tiny amount of code we could drop from the n-d implementation, since it seems libcanberra is/will be better taken care of, at least for now). Either way, it would be nice to at least see the notification stuff imported into GNOME's tree, where more people are likely to put eyes on it and be able to do things such as roll releases, squash a couple of tiny leaks Ubuntu is shipping patches for, etc. It would be a big step forward just to get that far. Hell, I know almost nothing about its internals but still would be willing to become a maintainer if needed (maybe I wouldn't do much in terms of real programming time but I sure can review and commit patches). It's just too useful to let it bit-rot. Over time we can adjust the feature set and/or the API (should not be a huge problem as long as we update libnotify as well). -- Patryk Zawadzki ___ desktop-devel-list mailing list desktop-devel-list@gnome.org http://mail.gnome.org/mailman/listinfo/desktop-devel-list ___ desktop-devel-list mailing list desktop-devel-list@gnome.org http://mail.gnome.org/mailman/listinfo/desktop-devel-list !DSPAM:1,491f6b0279881849514745! ___ desktop-devel-list mailing list desktop-devel-list@gnome.org http://mail.gnome.org/mailman/listinfo/desktop-devel-list !DSPAM:1,491f6b0279881849514745! signature.asc Description: This is a digitally signed message part ___ desktop-devel-list mailing list desktop-devel-list@gnome.org http://mail.gnome.org/mailman/listinfo/desktop-devel-list
Re: new module proposal: notification-daemon+libnotify
Hi, It's overhere http://svn.galago-project.org/trunk/ Jaap 2008/11/16 natan yellin [EMAIL PROTECTED]: Where is the code currently hosted? I'd like to play around with this if I have time. -Natan 2008/11/6 Christian Hammond [EMAIL PROTECTED] I can assure you that this hasn't bit-rotted. It has been in development, but my work on Unity at VMware this past year basically took up all my free time. I would be happy to have people who want to contribute and fix bugs. I plan to keep the roll as maintainer, and have a couple people in mind for a co-maintainer. If people really want certain things in or fixed, by all means, submit patches. Nobody has done so in a while and nobody's really been complaining about anything to my knowledge, so I haven't felt that a release was that urgent. Still, there are some important fixes in SVN, some of which were waiting for additional patches that I never got and only recently had time to finish up. I should be in a good position to do a release soon. Christian -- Christian Hammond - [EMAIL PROTECTED] VMware, Inc. On Thu, Nov 6, 2008 at 8:46 AM, Patryk Zawadzki [EMAIL PROTECTED] wrote: On Thu, Nov 6, 2008 at 5:30 PM, A. Walton [EMAIL PROTECTED] wrote: There are other maintenance-related issues to bring up as well, like the duplicated functionality in having both notification-daemon+libnotify and libcanberra doing sound notifications (tiny amount of code we could drop from the n-d implementation, since it seems libcanberra is/will be better taken care of, at least for now). Either way, it would be nice to at least see the notification stuff imported into GNOME's tree, where more people are likely to put eyes on it and be able to do things such as roll releases, squash a couple of tiny leaks Ubuntu is shipping patches for, etc. It would be a big step forward just to get that far. Hell, I know almost nothing about its internals but still would be willing to become a maintainer if needed (maybe I wouldn't do much in terms of real programming time but I sure can review and commit patches). It's just too useful to let it bit-rot. Over time we can adjust the feature set and/or the API (should not be a huge problem as long as we update libnotify as well). -- Patryk Zawadzki ___ desktop-devel-list mailing list desktop-devel-list@gnome.org http://mail.gnome.org/mailman/listinfo/desktop-devel-list ___ desktop-devel-list mailing list desktop-devel-list@gnome.org http://mail.gnome.org/mailman/listinfo/desktop-devel-list ___ desktop-devel-list mailing list desktop-devel-list@gnome.org http://mail.gnome.org/mailman/listinfo/desktop-devel-list ___ desktop-devel-list mailing list desktop-devel-list@gnome.org http://mail.gnome.org/mailman/listinfo/desktop-devel-list
Re: new module proposal: notification-daemon+libnotify
Where is the code currently hosted? I'd like to play around with this if I have time. -Natan 2008/11/6 Christian Hammond [EMAIL PROTECTED] I can assure you that this hasn't bit-rotted. It has been in development, but my work on Unity at VMware this past year basically took up all my free time. I would be happy to have people who want to contribute and fix bugs. I plan to keep the roll as maintainer, and have a couple people in mind for a co-maintainer. If people really want certain things in or fixed, by all means, submit patches. Nobody has done so in a while and nobody's really been complaining about anything to my knowledge, so I haven't felt that a release was that urgent. Still, there are some important fixes in SVN, some of which were waiting for additional patches that I never got and only recently had time to finish up. I should be in a good position to do a release soon. Christian -- Christian Hammond - [EMAIL PROTECTED] VMware, Inc. On Thu, Nov 6, 2008 at 8:46 AM, Patryk Zawadzki [EMAIL PROTECTED]wrote: On Thu, Nov 6, 2008 at 5:30 PM, A. Walton [EMAIL PROTECTED] wrote: There are other maintenance-related issues to bring up as well, like the duplicated functionality in having both notification-daemon+libnotify and libcanberra doing sound notifications (tiny amount of code we could drop from the n-d implementation, since it seems libcanberra is/will be better taken care of, at least for now). Either way, it would be nice to at least see the notification stuff imported into GNOME's tree, where more people are likely to put eyes on it and be able to do things such as roll releases, squash a couple of tiny leaks Ubuntu is shipping patches for, etc. It would be a big step forward just to get that far. Hell, I know almost nothing about its internals but still would be willing to become a maintainer if needed (maybe I wouldn't do much in terms of real programming time but I sure can review and commit patches). It's just too useful to let it bit-rot. Over time we can adjust the feature set and/or the API (should not be a huge problem as long as we update libnotify as well). -- Patryk Zawadzki ___ desktop-devel-list mailing list desktop-devel-list@gnome.org http://mail.gnome.org/mailman/listinfo/desktop-devel-list ___ desktop-devel-list mailing list desktop-devel-list@gnome.org http://mail.gnome.org/mailman/listinfo/desktop-devel-list ___ desktop-devel-list mailing list desktop-devel-list@gnome.org http://mail.gnome.org/mailman/listinfo/desktop-devel-list
Re: new module proposal: notification-daemon+libnotify
On Fri, 2008-11-07 at 13:09 +, Calum Benson wrote: On 6 Nov 2008, at 17:38, David Zeuthen wrote: But not all notifications comes from applications launched by the user. For example There is a high probability that one or more of your hard disk will malfunction within the next 24 hours Your laptop battery is being recalled Security updates available I'm not sure where we'd display stuff like this except for using icons in the notification area. Some sort of status icon change with an appropriate tooltip would probably be sufficient for things that don't need immediate attention. For things that do, or for which there is no status icon, an alert box is often more appropriate anyway. wasn't libnotify/notification-daemon created to replace alert boxes? I tend to find them quite useless, since I miss them most of the time while typing without looking at the screen, so I don't think they are a good solution for immediate attention stuff -- Rodrigo Moya [EMAIL PROTECTED] ___ desktop-devel-list mailing list desktop-devel-list@gnome.org http://mail.gnome.org/mailman/listinfo/desktop-devel-list
Re: new module proposal: notification-daemon+libnotify
I sometimes miss my notifications too.. Would it be possible to remember notifications that have come through until they are explicitly acknowledged? We could bind some key to doing this, so that you press that key when the notification is showing to acknowledge it. For missed notifications, we could leave an icon in the notification area. When you click that icon it might show you all the unacknowledged notifications until clicked again. You'd probably need some button on all the notices to mark them as acknowledged. As a user, there are many things I like to be notified in the way that libnotification allows. There are also some notifications that you won't care about missing, such as now playing song X. I think notification daemon should be accepted, but I don't think it should be used for critical notifications (i.e your battery will explode in 25 seconds) unless there is some way of pulling up ones you missed. For extra points, if the message says anything about parts about to explode or catch fire, the daemon should generate a png to reiterate this text and set it as your background :-) Cheers, Martin On Mon, Nov 10, 2008 at 8:28 AM, Rodrigo Moya [EMAIL PROTECTED] wrote: On Fri, 2008-11-07 at 13:09 +, Calum Benson wrote: On 6 Nov 2008, at 17:38, David Zeuthen wrote: But not all notifications comes from applications launched by the user. For example There is a high probability that one or more of your hard disk will malfunction within the next 24 hours Your laptop battery is being recalled Security updates available I'm not sure where we'd display stuff like this except for using icons in the notification area. Some sort of status icon change with an appropriate tooltip would probably be sufficient for things that don't need immediate attention. For things that do, or for which there is no status icon, an alert box is often more appropriate anyway. wasn't libnotify/notification-daemon created to replace alert boxes? I tend to find them quite useless, since I miss them most of the time while typing without looking at the screen, so I don't think they are a good solution for immediate attention stuff -- Rodrigo Moya [EMAIL PROTECTED] ___ desktop-devel-list mailing list desktop-devel-list@gnome.org http://mail.gnome.org/mailman/listinfo/desktop-devel-list ___ desktop-devel-list mailing list desktop-devel-list@gnome.org http://mail.gnome.org/mailman/listinfo/desktop-devel-list
Re: new module proposal: notification-daemon+libnotify
On Mon, Nov 10, 2008 at 9:11 AM, Martin Meyer [EMAIL PROTECTED] wrote: I sometimes miss my notifications too.. Would it be possible to remember notifications that have come through until they are explicitly acknowledged? We could bind some key to doing this, so that you press that key when the notification is showing to acknowledge it. For missed notifications, we could leave an icon in the notification area. When you click that icon it might show you all the unacknowledged notifications until clicked again. You'd probably need some button on all the notices to mark them as acknowledged. Some ideas for better handling of notifications can be found here: http://live.gnome.org/AlternativeNotificationsUI ___ desktop-devel-list mailing list desktop-devel-list@gnome.org http://mail.gnome.org/mailman/listinfo/desktop-devel-list
Re: new module proposal: notification-daemon+libnotify
On 11/10/08, Matthias Clasen [EMAIL PROTECTED] wrote: On Mon, Nov 10, 2008 at 9:11 AM, Martin Meyer [EMAIL PROTECTED] wrote: I sometimes miss my notifications too.. Would it be possible to remember notifications that have come through until they are explicitly acknowledged? We could bind some key to doing this, so that you press that key when the notification is showing to acknowledge it. For missed notifications, we could leave an icon in the notification area. When you click that icon it might show you all the unacknowledged notifications until clicked again. You'd probably need some button on all the notices to mark them as acknowledged. Some ideas for better handling of notifications can be found here: http://live.gnome.org/AlternativeNotificationsUI Nice. Have you seen any of the ideas suggested at the hackfest? http://live.gnome.org/Boston2008/GUIHackfest/WindowManagementAndMore http://live.gnome.org/Boston2008/GUIHackfest/WindowManagement Also see http://live.gnome.org/Mathusalem. ___ desktop-devel-list mailing list desktop-devel-list@gnome.org http://mail.gnome.org/mailman/listinfo/desktop-devel-list ___ desktop-devel-list mailing list desktop-devel-list@gnome.org http://mail.gnome.org/mailman/listinfo/desktop-devel-list
Re: new module proposal: notification-daemon+libnotify
On Mon, 2008-11-10 at 09:37 -0500, Matthias Clasen wrote: On Mon, Nov 10, 2008 at 9:11 AM, Martin Meyer [EMAIL PROTECTED] wrote: I sometimes miss my notifications too.. Would it be possible to remember notifications that have come through until they are explicitly acknowledged? We could bind some key to doing this, so that you press that key when the notification is showing to acknowledge it. For missed notifications, we could leave an icon in the notification area. When you click that icon it might show you all the unacknowledged notifications until clicked again. You'd probably need some button on all the notices to mark them as acknowledged. Some ideas for better handling of notifications can be found here: http://live.gnome.org/AlternativeNotificationsUI it looks nice, but where would immediate-action-required notifications be shown? Things like 'your battery is about to die'? -- Rodrigo Moya [EMAIL PROTECTED] ___ desktop-devel-list mailing list desktop-devel-list@gnome.org http://mail.gnome.org/mailman/listinfo/desktop-devel-list
Re: new module proposal: notification-daemon+libnotify
On Mon, 2008-11-10 at 17:55 +0100, Rodrigo Moya wrote: On Mon, 2008-11-10 at 09:37 -0500, Matthias Clasen wrote: On Mon, Nov 10, 2008 at 9:11 AM, Martin Meyer [EMAIL PROTECTED] wrote: I sometimes miss my notifications too.. Would it be possible to remember notifications that have come through until they are explicitly acknowledged? We could bind some key to doing this, so that you press that key when the notification is showing to acknowledge it. For missed notifications, we could leave an icon in the notification area. When you click that icon it might show you all the unacknowledged notifications until clicked again. You'd probably need some button on all the notices to mark them as acknowledged. Some ideas for better handling of notifications can be found here: http://live.gnome.org/AlternativeNotificationsUI it looks nice, but where would immediate-action-required notifications be shown? Things like 'your battery is about to die'? Stay-on-top, non-focus-stealing dialogues without any close button. Goes away when you plug your laptop into the mains. ___ desktop-devel-list mailing list desktop-devel-list@gnome.org http://mail.gnome.org/mailman/listinfo/desktop-devel-list
Re: new module proposal: notification-daemon+libnotify
Some ideas for better handling of notifications can be found here: http://live.gnome.org/AlternativeNotificationsUI it looks nice, but where would immediate-action-required notifications be shown? Things like 'your battery is about to die'? Stay-on-top, non-focus-stealing dialogues without any close button. Goes away when you plug your laptop into the mains. Heh - these are the kinds of dialogs I want to assassinate when I'm giving a presentation. Will ___ desktop-devel-list mailing list desktop-devel-list@gnome.org http://mail.gnome.org/mailman/listinfo/desktop-devel-list
Re: new module proposal: notification-daemon+libnotify
2008-11-10 klockan 15:11 skrev Martin Meyer: I sometimes miss my notifications too.. Would it be possible to remember notifications that have come through until they are explicitly acknowledged? We could bind some key to doing this, so that you press that key when the notification is showing to acknowledge it. For missed notifications, we could leave an icon in the notification area. When you click that icon it might show you all the unacknowledged notifications until clicked again. You'd probably need some button on all the notices to mark them as acknowledged. If I remember correctly, notifications shown by the leave a message functionality in Gnome Screensaver do not close until you actually click them. — Wouter P.S. Note that I don't agree with notifications for this purpose in Gnome Screensaver. See bug 471845 and 384509 for more information: http://bugzilla.gnome.org/show_bug.cgi?id=471845 and http://bugzilla.gnome.org/show_bug.cgi?id=384509 -- :wq mail [EMAIL PROTECTED] web http://uwstopia.nl i wanna give you everything · i wanna give you energy — underworld signature.asc Description: Digital signature ___ desktop-devel-list mailing list desktop-devel-list@gnome.org http://mail.gnome.org/mailman/listinfo/desktop-devel-list
Re: new module proposal: notification-daemon+libnotify
Very critical notifications can be set to have a non-expiring timeout. This would ensure that they stay visible until the user acknowledges them. Some people have also talked about writing a notification backlog for important notifications, where an icon in the tray blinks when there's certain notifications you missed. The problem with this is that you really need to have a fine-grained concept of what's important and should trigger the blinking. You could leave it at critical notifications and you might be fine, but these may as well just be set to not disappear by the calling program if it's really important (your battery is going to explode). Christian -- Christian Hammond - [EMAIL PROTECTED] VMware, Inc. On Mon, Nov 10, 2008 at 6:11 AM, Martin Meyer [EMAIL PROTECTED] wrote: I sometimes miss my notifications too.. Would it be possible to remember notifications that have come through until they are explicitly acknowledged? We could bind some key to doing this, so that you press that key when the notification is showing to acknowledge it. For missed notifications, we could leave an icon in the notification area. When you click that icon it might show you all the unacknowledged notifications until clicked again. You'd probably need some button on all the notices to mark them as acknowledged. As a user, there are many things I like to be notified in the way that libnotification allows. There are also some notifications that you won't care about missing, such as now playing song X. I think notification daemon should be accepted, but I don't think it should be used for critical notifications (i.e your battery will explode in 25 seconds) unless there is some way of pulling up ones you missed. For extra points, if the message says anything about parts about to explode or catch fire, the daemon should generate a png to reiterate this text and set it as your background :-) Cheers, Martin On Mon, Nov 10, 2008 at 8:28 AM, Rodrigo Moya [EMAIL PROTECTED] wrote: On Fri, 2008-11-07 at 13:09 +, Calum Benson wrote: On 6 Nov 2008, at 17:38, David Zeuthen wrote: But not all notifications comes from applications launched by the user. For example There is a high probability that one or more of your hard disk will malfunction within the next 24 hours Your laptop battery is being recalled Security updates available I'm not sure where we'd display stuff like this except for using icons in the notification area. Some sort of status icon change with an appropriate tooltip would probably be sufficient for things that don't need immediate attention. For things that do, or for which there is no status icon, an alert box is often more appropriate anyway. wasn't libnotify/notification-daemon created to replace alert boxes? I tend to find them quite useless, since I miss them most of the time while typing without looking at the screen, so I don't think they are a good solution for immediate attention stuff -- Rodrigo Moya [EMAIL PROTECTED] ___ desktop-devel-list mailing list desktop-devel-list@gnome.org http://mail.gnome.org/mailman/listinfo/desktop-devel-list ___ desktop-devel-list mailing list desktop-devel-list@gnome.org http://mail.gnome.org/mailman/listinfo/desktop-devel-list ___ desktop-devel-list mailing list desktop-devel-list@gnome.org http://mail.gnome.org/mailman/listinfo/desktop-devel-list
Re: new module proposal: notification-daemon+libnotify
Hey Christian, 2008/11/10 Christian Hammond [EMAIL PROTECTED]: Very critical notifications can be set to have a non-expiring timeout. This would ensure that they stay visible until the user acknowledges them. Some people have also talked about writing a notification backlog for important notifications, where an icon in the tray blinks when there's certain notifications you missed. The problem with this is that you really need to have a fine-grained concept of what's important and should trigger the blinking. You could leave it at critical notifications and you might be fine, but these may as well just be set to not disappear by the calling program if it's really important (your battery is going to explode). Yes, I'd like to see this too. There are a number of reasons why it would be useful to have an obvious way to view a record of notifications. * Queue all messages while away * Queue messages (except critical) while busy * Queue messages (except critical) while in fullscreen * Hide all but important (but user configurable) messages by default * Access messages later that were dismissed by mistake (ie. be forgiving) * Provide a way to see missed messages or messages that timed out before I could read them * Provide an API to screensaver/display-manager to get number of unread messages * Minimize distraction for less than important messages * Remind me of when a message arrived (eg. oh man has it been an hour already since that appointment reminder) * Provide a way to discriminate what is important enough to disrupt me (blinking is pretty severe, colors/boldness may work) * Allow the user to configure what is important to them or what they never want to see (ie. put the user in control) * Allow the user to use the bubble to quickly decide whether the item needs immediate attention but have the freedom to access it later (after the bubble times out). [1] Jon [1] A good use case here is an instant message conversation. I probably want to see a bubble for the first message from a friend. But I don't necessarily want to respond immediately. And if I choose not to respond immediately I still want to have an easy access to that message. Also, I probably don't want to see another bubble message from that friend until I respond once. However, it may be useful to increment a counter on the status icon that represents the message history (aka. the notification center). Facebook and Adium have good examples of this type of status icon. ___ desktop-devel-list mailing list desktop-devel-list@gnome.org http://mail.gnome.org/mailman/listinfo/desktop-devel-list
Re: new module proposal: notification-daemon+libnotify
On Mon, 2008-11-10 at 15:30 -0500, Willie Walker wrote: Some ideas for better handling of notifications can be found here: http://live.gnome.org/AlternativeNotificationsUI it looks nice, but where would immediate-action-required notifications be shown? Things like 'your battery is about to die'? Stay-on-top, non-focus-stealing dialogues without any close button. Goes away when you plug your laptop into the mains. Heh - these are the kinds of dialogs I want to assassinate when I'm giving a presentation. That's the kind of dialogues that are accessible and give you just the right amount of annoyance to make sure you get rid of them. This is for I'm about to shut down if you don't do anything right now, not for battery's only got 20 minutes of life left. I think we could get rid of most of our notification popups if only the icons they belonged to were always at the same location (meaning that checking the battery would only be a glance away, not a hard-look and a stare away as it currently is). ___ desktop-devel-list mailing list desktop-devel-list@gnome.org http://mail.gnome.org/mailman/listinfo/desktop-devel-list
Re: new module proposal: notification-daemon+libnotify
On 6 Nov 2008, at 17:38, David Zeuthen wrote: But not all notifications comes from applications launched by the user. For example There is a high probability that one or more of your hard disk will malfunction within the next 24 hours Your laptop battery is being recalled Security updates available I'm not sure where we'd display stuff like this except for using icons in the notification area. Some sort of status icon change with an appropriate tooltip would probably be sufficient for things that don't need immediate attention. For things that do, or for which there is no status icon, an alert box is often more appropriate anyway. Which doesn't sound like a winning scenario either (granted for the latter two we do have icons in the notification area; probably not for the former (we could do that though)). It would be good if the HIG covered this. Yeah, there's an embryonic section in the draft HIG that never got finished :/ It remains to be seen whether the HIG will actually see any more activity before all this new desktop shell stuff sees the light of day... but I'd like to think we can finish some of those pending updates and push out one more version. Cheeri, Calum. -- CALUM BENSON, Usability Engineer Sun Microsystems Ireland mailto:[EMAIL PROTECTED]GNOME Desktop Team http://blogs.sun.com/calum +353 1 819 9771 Any opinions are personal and not necessarily those of Sun Microsystems ___ desktop-devel-list mailing list desktop-devel-list@gnome.org http://mail.gnome.org/mailman/listinfo/desktop-devel-list
Re: new module proposal: notification-daemon+libnotify
Calum Benson wrote on 07/11/08 13:09: On 6 Nov 2008, at 17:38, David Zeuthen wrote: ... There is a high probability that one or more of your hard disk will malfunction within the next 24 hours Your laptop battery is being recalled Security updates available I'm not sure where we'd display stuff like this except for using icons in the notification area. Some sort of status icon change with an appropriate tooltip would probably be sufficient for things that don't need immediate attention. For things that do, or for which there is no status icon, an alert box is often more appropriate anyway. With my Ubuntu hat on, I'll go a little further than that, and say we really would rather application developers didn't use status icons *or* notification bubbles for critical situations like those in David's examples. (Other distributors may, of course, have different opinions.) Status icons are often ignored or not noticed, especially when there are many of them, and notification bubbles work best when they go away by themselves. So while both of them have a purpose, neither of them are suitable for things that people really positively need to respond to. If there is no more pleasant window in which to convey a critical situation like that, use an alert. Cheers -- Matthew Paul Thomas http://mpt.net.nz/ ___ desktop-devel-list mailing list desktop-devel-list@gnome.org http://mail.gnome.org/mailman/listinfo/desktop-devel-list
Re: new module proposal: notification-daemon+libnotify
On Thu, Oct 30, 2008 at 9:40 AM, Bastien Nocera [EMAIL PROTECTED] wrote: On Thu, 2008-10-30 at 10:24 -0400, Colin Walters wrote: Yes, I know what your initial reaction is - again?. Only maintainers can propose new modules, so unless we're talking external dependency, Christian would have to write that mail... I don't know how busy Christian is. But even if he is too busy to propose the module himself, I think it is time for us to be honest about the fact that it is pretty much impossible to use the desktop without notification-daemon nowadays. Many components rely on the ability to notify users in this way and are severely reduced in functionality if the notification service is not available. Sure, the implementation may not be ideal, and in an ideal world, it would not have its own little theming island and would maybe just be part of the desktop shell, but we don't live in that world (yet ?). Matthias ___ desktop-devel-list mailing list desktop-devel-list@gnome.org http://mail.gnome.org/mailman/listinfo/desktop-devel-list
Re: new module proposal: notification-daemon+libnotify
Le jeudi 06 novembre 2008, à 10:57 -0500, Matthias Clasen a écrit : I don't know how busy Christian is. But even if he is too busy to propose the module himself, I think it is time for us to be honest about the fact that it is pretty much impossible to use the desktop without notification-daemon nowadays. Many components rely on the ability to notify users in this way and are severely reduced in functionality if the notification service is not available. Sure, the implementation may not be ideal, and in an ideal world, it would not have its own little theming island and would maybe just be part of the desktop shell, but we don't live in that world (yet ?). I'm more worried about the fact that there has been no release since early 2007 (if I'm not mistaken), and so distro are currently shipping it with patches. Maybe we can just import the module in GNOME svn and fix stuff there? Vincent -- Les gens heureux ne sont pas pressés. ___ desktop-devel-list mailing list desktop-devel-list@gnome.org http://mail.gnome.org/mailman/listinfo/desktop-devel-list
Re: new module proposal: notification-daemon+libnotify
On 6 Nov 2008, at 15:57, Matthias Clasen wrote: But even if he is too busy to propose the module himself, I think it is time for us to be honest about the fact that it is pretty much impossible to use the desktop without notification-daemon nowadays. Many components rely on the ability to notify users in this way and are severely reduced in functionality if the notification service is not available. Anything that *relies* on this kind of notification is kind of broken IMHO, usability-wise (and probably accessibility-wise, too). Notification messages are really just status bar messages for the desktop. As such, they should be there to provide useful extra information if you want them to, but equally you should be able to switch them off altogether without adversely affecting your ability to use any applications. Cheeri, Calum. -- CALUM BENSON, Usability Engineer Sun Microsystems Ireland mailto:[EMAIL PROTECTED]GNOME Desktop Team http://blogs.sun.com/calum +353 1 819 9771 Any opinions are personal and not necessarily those of Sun Microsystems ___ desktop-devel-list mailing list desktop-devel-list@gnome.org http://mail.gnome.org/mailman/listinfo/desktop-devel-list
Re: new module proposal: notification-daemon+libnotify
On Thu, Nov 6, 2008 at 11:00 AM, Vincent Untz [EMAIL PROTECTED] wrote: Le jeudi 06 novembre 2008, à 10:57 -0500, Matthias Clasen a écrit : I don't know how busy Christian is. But even if he is too busy to propose the module himself, I think it is time for us to be honest about the fact that it is pretty much impossible to use the desktop without notification-daemon nowadays. Many components rely on the ability to notify users in this way and are severely reduced in functionality if the notification service is not available. Sure, the implementation may not be ideal, and in an ideal world, it would not have its own little theming island and would maybe just be part of the desktop shell, but we don't live in that world (yet ?). I'm more worried about the fact that there has been no release since early 2007 (if I'm not mistaken), and so distro are currently shipping it with patches. Maybe we can just import the module in GNOME svn and fix stuff there? There are other maintenance-related issues to bring up as well, like the duplicated functionality in having both notification-daemon+libnotify and libcanberra doing sound notifications (tiny amount of code we could drop from the n-d implementation, since it seems libcanberra is/will be better taken care of, at least for now). Either way, it would be nice to at least see the notification stuff imported into GNOME's tree, where more people are likely to put eyes on it and be able to do things such as roll releases, squash a couple of tiny leaks Ubuntu is shipping patches for, etc. It would be a big step forward just to get that far. -A. Walton Vincent -- Les gens heureux ne sont pas pressés. ___ desktop-devel-list mailing list desktop-devel-list@gnome.org http://mail.gnome.org/mailman/listinfo/desktop-devel-list ___ desktop-devel-list mailing list desktop-devel-list@gnome.org http://mail.gnome.org/mailman/listinfo/desktop-devel-list
Re: new module proposal: notification-daemon+libnotify
But even if he is too busy to propose the module himself, I think it is time for us to be honest about the fact that it is pretty much impossible to use the desktop without notification-daemon nowadays. I can only second that. Some while ago, I offered g-s-d to use notification for all kind of error that might happen (well, under normal circumstances g-s-d is 100% silent, but you know that far-from-perfect world...). But it could not be done without blessed dependency. g-s-d is complex enough to be completely bug-free - but usually in case of g-s-d misbehaves it is not easy to find out what exactly happened - partially, because we do not have desktop-wide logging facilities. At least, using libnotify could improve things a bit (keeping g-s-d independent from X at the same time). Cheers, Sergey ___ desktop-devel-list mailing list desktop-devel-list@gnome.org http://mail.gnome.org/mailman/listinfo/desktop-devel-list
Re: new module proposal: notification-daemon+libnotify
On Thu, 2008-11-06 at 17:00 +0100, Vincent Untz wrote: I'm more worried about the fact that there has been no release since early 2007 (if I'm not mistaken), and so distro are currently shipping it with patches. Maybe we can just import the module in GNOME svn and fix stuff there? Yes, this seems a good idea to me. If we want to do this and are lacking a volunteer for importing/reviewing patches and bugs you can count me in :) Cheers, Cosimo ___ desktop-devel-list mailing list desktop-devel-list@gnome.org http://mail.gnome.org/mailman/listinfo/desktop-devel-list
Re: new module proposal: notification-daemon+libnotify
I would *love* to see this bug get fixed: http://trac.galago-project.org/ticket/91 Will On Thu, 2008-11-06 at 19:43 +0100, Cosimo Cecchi wrote: On Thu, 2008-11-06 at 17:00 +0100, Vincent Untz wrote: I'm more worried about the fact that there has been no release since early 2007 (if I'm not mistaken), and so distro are currently shipping it with patches. Maybe we can just import the module in GNOME svn and fix stuff there? Yes, this seems a good idea to me. If we want to do this and are lacking a volunteer for importing/reviewing patches and bugs you can count me in :) Cheers, Cosimo ___ desktop-devel-list mailing list desktop-devel-list@gnome.org http://mail.gnome.org/mailman/listinfo/desktop-devel-list ___ desktop-devel-list mailing list desktop-devel-list@gnome.org http://mail.gnome.org/mailman/listinfo/desktop-devel-list
Re: new module proposal: notification-daemon+libnotify
Hi everyone. So, yes, I've been pretty busy as of late and haven't done a release in a while. I've been waiting on some work to be finished for a patch for notification-daemon these past couple of months and have decided it can wait. I'll be performing a release shortly. I actually meant to do this about two weeks ago, but have had some stuff going on in my life that's delayed this. Hopefully this weekend. As far as patches go, I've noticed that some distros are shipping patches that have never come across to me. If there are distros with patches that are not in notification-daemon SVN, please do send them my way so I can include them for the release. The tentative plan for notification-daemon and libnotify is to move them into SVN and switch over to Bugzilla. I'm then hoping to get someone to act as a co-maintainer for this. There will be a formal code review process for these modules, using a Review Board installation I'm setting up. All code will be expected to go through this before being committed in the code base (aside from translations). I would also like to formally propose notification-daemon and libnotify for inclusion into GNOME. To be quite honest, I've in the past lost interest in proposing this because it was rejected time and time again despite half the desktop depending on it nowadays, and I just left things up to the various distros to decide whether to provide the full functionality of these applications. However, I would like to get this into the GNOME desktop and as someone before said, I think we need to be realistic about the fact that this is pretty heavily used now and is in essence a dependency already. Christian -- Christian Hammond - [EMAIL PROTECTED] VMware, Inc. On Thu, Nov 6, 2008 at 10:43 AM, Cosimo Cecchi [EMAIL PROTECTED] wrote: On Thu, 2008-11-06 at 17:00 +0100, Vincent Untz wrote: I'm more worried about the fact that there has been no release since early 2007 (if I'm not mistaken), and so distro are currently shipping it with patches. Maybe we can just import the module in GNOME svn and fix stuff there? Yes, this seems a good idea to me. If we want to do this and are lacking a volunteer for importing/reviewing patches and bugs you can count me in :) Cheers, Cosimo ___ desktop-devel-list mailing list desktop-devel-list@gnome.org http://mail.gnome.org/mailman/listinfo/desktop-devel-list ___ desktop-devel-list mailing list desktop-devel-list@gnome.org http://mail.gnome.org/mailman/listinfo/desktop-devel-list
Re: new module proposal: notification-daemon+libnotify
I can assure you that this hasn't bit-rotted. It has been in development, but my work on Unity at VMware this past year basically took up all my free time. I would be happy to have people who want to contribute and fix bugs. I plan to keep the roll as maintainer, and have a couple people in mind for a co-maintainer. If people really want certain things in or fixed, by all means, submit patches. Nobody has done so in a while and nobody's really been complaining about anything to my knowledge, so I haven't felt that a release was that urgent. Still, there are some important fixes in SVN, some of which were waiting for additional patches that I never got and only recently had time to finish up. I should be in a good position to do a release soon. Christian -- Christian Hammond - [EMAIL PROTECTED] VMware, Inc. On Thu, Nov 6, 2008 at 8:46 AM, Patryk Zawadzki [EMAIL PROTECTED]wrote: On Thu, Nov 6, 2008 at 5:30 PM, A. Walton [EMAIL PROTECTED] wrote: There are other maintenance-related issues to bring up as well, like the duplicated functionality in having both notification-daemon+libnotify and libcanberra doing sound notifications (tiny amount of code we could drop from the n-d implementation, since it seems libcanberra is/will be better taken care of, at least for now). Either way, it would be nice to at least see the notification stuff imported into GNOME's tree, where more people are likely to put eyes on it and be able to do things such as roll releases, squash a couple of tiny leaks Ubuntu is shipping patches for, etc. It would be a big step forward just to get that far. Hell, I know almost nothing about its internals but still would be willing to become a maintainer if needed (maybe I wouldn't do much in terms of real programming time but I sure can review and commit patches). It's just too useful to let it bit-rot. Over time we can adjust the feature set and/or the API (should not be a huge problem as long as we update libnotify as well). -- Patryk Zawadzki ___ desktop-devel-list mailing list desktop-devel-list@gnome.org http://mail.gnome.org/mailman/listinfo/desktop-devel-list ___ desktop-devel-list mailing list desktop-devel-list@gnome.org http://mail.gnome.org/mailman/listinfo/desktop-devel-list
new module proposal: notification-daemon+libnotify
Yes, I know what your initial reaction is - again?. Going back to http://mail.gnome.org/archives/desktop-devel-list/2007-September/msg00533.html Which was followed up here: http://mail.gnome.org/archives/desktop-devel-list/2007-September/msg00537.html Which I think is a pretty good summary, and I think addressed the objections. One side note is that with the introspection work, adding new libraries isn't a total mess for bindings and distributors. I think Christian plans to get notification-daemon and libnotify in GNOME SVN and using Bugzilla as well. ___ desktop-devel-list mailing list desktop-devel-list@gnome.org http://mail.gnome.org/mailman/listinfo/desktop-devel-list
Re: new module proposal: notification-daemon+libnotify
On Thu, 2008-10-30 at 10:24 -0400, Colin Walters wrote: Yes, I know what your initial reaction is - again?. Only maintainers can propose new modules, so unless we're talking external dependency, Christian would have to write that mail... Cheers ___ desktop-devel-list mailing list desktop-devel-list@gnome.org http://mail.gnome.org/mailman/listinfo/desktop-devel-list
