search

fastsupply / growl

Automatically exported from code.google.com/p/growl
0 stars 0 forks source link

Investigate notifying for every app except the active app #113

Open GoogleCodeExporter opened 9 years ago

GoogleCodeExporter commented 9 years ago 
Investigate whether this is more usable than the current status quo:

Whenever an application is in front, do not send a notification for it.

Related to ticket #111

Original issue reported on code.google.com by chrisf.g...@gmail.com on 12 Mar 2010 at 5:13

GoogleCodeExporter commented 9 years ago 
I think a pref for this would be fair.

Original comment by prhgr...@gmail.com on 12 Mar 2010 at 9:58

GoogleCodeExporter commented 9 years ago 
I agree. I'm wondering if it should be the default, maybe in 1.3.

Original comment by chrisf.g...@gmail.com on 13 Mar 2010 at 3:19

GoogleCodeExporter commented 9 years ago 
Moving to 2.0.

Original comment by chrisf.g...@gmail.com on 29 Jul 2010 at 4:41

GoogleCodeExporter commented 9 years ago 
We should have this in 2.0.

Original comment by chrisf.g...@gmail.com on 29 Jul 2010 at 10:06

GoogleCodeExporter commented 9 years ago

Original comment by chrisf.g...@gmail.com on 31 May 2011 at 7:32

GoogleCodeExporter commented 9 years ago 
I'm not sure that this makes sense as the default in all cases.  In some, 
certainly: if I'm uploading a file in Transmit, I probably don't care about 
seeing the 'upload complete' Growl notification if Transmit is the active app.

On the other hand, let's say I'm using Adium or Trillian; I'm in Chat A, and 
someone sends me a message in Chat B (which is currently not the focused chat). 
 I probably want to see the message content, not just a badged '(1)' for unread 
messages in that tab.  Or let's say I'm using Colloquy, and I'm in #channel1 
and someone mentions a trigger word in #channel2.  I probably want the Growl 
notice showing that someone's mentioned a trigger word in that channel, since 
I'm not in the channel.

Speaking from the third-party developer side, I'm pretty sure that if the 
default behavior changed to hide all Growl notices when the app is focused, I 
-- and the Adium and Colloquy -- developers would get bug reports of "Can't see 
notices for messages in other tabs anymore!  It's broken!"

Original comment by cerulean...@gmail.com on 31 May 2011 at 7:41

GoogleCodeExporter commented 9 years ago 
Agreed; Adium would not like this functionality change.

Do any users even want this change? Feels like notifications are useful 
regardless of app-in-front status.

Original comment by zacw...@gmail.com on 31 May 2011 at 8:50

GoogleCodeExporter commented 9 years ago 
We can hold off on this until 2.0 and see how things differ with the rollup 
window in 1.3. My concern here is with screen spam. I also thought it was 
pretty cool when Panic added this to their FTP client, which is where this 
ticket spawned from.

I can see what you guys are saying about the usage. I talked to prh about 
making a way for applications to make an exception, but he brought up a valid 
point that if users do like this then they wouldn't want random applications to 
make an exception.

I do think that this should have a preference if it is in Growl, as mentioned 
by prh and myself earlier up in this ticket.

Original comment by chrisf.g...@gmail.com on 31 May 2011 at 10:31

GoogleCodeExporter commented 9 years ago 
I would further suggest that it should be a per-application preference.

Original comment by p...@growl.info on 31 May 2011 at 10:44

GoogleCodeExporter commented 9 years ago 
If it's a per-application preference, I feel it should default to off (or allow 
an app a way to specify what the expected default is).  If it's a global 
preference, I /definitely/ feel it should default to 'off' rather than 'on' or 
else it will generate a lot of headaches for anyone who makes chat software.  

Changing established behavior will confuse a non-zero number of users, who will 
generate a non-zero number of bug tickets.

Original comment by cerulean...@gmail.com on 31 May 2011 at 10:55

GoogleCodeExporter commented 9 years ago 
Would this help:

http://code.google.com/p/growl/issues/detail?id=215

I think this would address the concerns brought up here, per application 
categories to define default behaviors.

Original comment by chrisf.g...@gmail.com on 31 May 2011 at 11:13

GoogleCodeExporter commented 9 years ago 
> Changing established behavior will confuse a non-zero number of users, who 
will generate a non-zero number of bug tickets.

…already a given, considering that its existence in the background behaviour 
of GrowlTunes already generates occasional confusion.

Original comment by I.atent.dead@gmail.com on 31 May 2011 at 11:15

GoogleCodeExporter commented 9 years ago 
ceruleansparks: I agree with comment #10 100%.

Original comment by p...@growl.info on 1 Jun 2011 at 2:15

GoogleCodeExporter commented 9 years ago 
So here's what I'm thinking.

In 1.3 introduce a general preference, disabled by default to allow for end 
users to enable this if they would like. Let some of our more intrepid users 
inform us as to whether this feature is something they like, how they would 
modify it, etc etc.

By time 2.0 comes around, we should have enough feedback to make a good case 
around how to work with this sort of feature (i.e. exceptions like the one 
ceruleansparks brought up in comment 10, which is a pretty valid point and led 
to ticket #215).

I have convinced myself that this is something which would make Growl that much 
more friendly to use. That said, the point that we need to proceed with caution 
when changing functionality is a good one. I think a staged process is the 
right way to accomplish that.

Original comment by chrisf.g...@gmail.com on 1 Jun 2011 at 2:29

GoogleCodeExporter commented 9 years ago

Original comment by chrisf.g...@gmail.com on 9 Jul 2011 at 6:16

GoogleCodeExporter commented 9 years ago 
I would love to see this implemented as an optional per-application preference.

While I agree that this could possibly create confusion if the user is unaware 
of the preference being enabled, I definitely see the practicality of 
implementing this type of thing, and I think the benefits outweigh the costs.

As another example of how this would be useful...

I have notifications set up for gmail chat (through a Fluid SSB app).  I really 
love getting the growl notifications when I'm doing something else on the 
computer (i.e. I have another app/window focused), so that I know if I receive 
a message.  However, when gmail chat already has my focus, and I'm in an active 
conversation, I would really rather not see the growl notifications for every 
single chat message I receive, since they just pile up, and I already know that 
I'm receiving messages.

Sorry if this point was already made, but I thought the example I gave was 
worth sharing.

Original comment by davejhil...@gmail.com on 18 Jul 2011 at 11:48

GoogleCodeExporter commented 9 years ago

Original comment by chrisf.g...@gmail.com on 11 Aug 2011 at 6:39

GoogleCodeExporter commented 9 years ago 
Changing the owner on these to get them out of Peter's queue.

Original comment by chrisf.g...@gmail.com on 15 Aug 2011 at 6:49

GoogleCodeExporter commented 9 years ago

Original comment by ch...@growl.info on 29 Sep 2011 at 12:12

GoogleCodeExporter commented 9 years ago

Original comment by ch...@growl.info on 11 Nov 2011 at 1:58

GoogleCodeExporter commented 9 years ago

Original comment by ch...@growl.info on 14 Nov 2011 at 12:43

GoogleCodeExporter commented 9 years ago

Original comment by ch...@growl.info on 19 Jan 2012 at 10:45

GoogleCodeExporter commented 9 years ago

Original comment by ch...@growl.info on 21 Jun 2012 at 4:38