Utilization of existing Growl

[mic92]

Utilization of existing Growl

[GoogleCodeExporter]

I'm not sure I understand what you're looking for - I *am* using Growl in my 
application.

Original comment by [email protected] on 8 Sep 2010 at 10:28

[GoogleCodeExporter]

Are you going from Phone -> Growl?   Or Phone -> Application -> Growl?   I'm 
interested in Phone -> Growl.

If you go directly to Growl, you don't need to worry about a PC/Linux client.  
As Growl is already is a solidly built notification application.

Original comment by [email protected] on 8 Sep 2010 at 11:32

[GoogleCodeExporter]

Right. So the Growl protocol is quite limited - I would be able to show text 
notifications, but the following features that the app provides would be 
impossible:
* Icons
* Bluetooth
* Notifying over TCP
* Encryption (future release)
* Commands (like replying to an SMS from the computer - future release)
* Filtering notifications by device
etc.

Given that, I can still implement it, but it shouldn't be the users' primary 
choice.

Original comment by [email protected] on 9 Sep 2010 at 12:22

[GoogleCodeExporter]

Growl's updated GNTP protocol allows for Icons, TCP, and encryptions.  
Filtering is built in.  Are Bluetooth and Commands really the majority of the 
userbase? 

Original comment by [email protected] on 9 Sep 2010 at 12:44

[GoogleCodeExporter]

Commands haven't been released yet, so I don't know.
About bluetooth, I'd say about half the users use it.

I thought GNTP were only supported in Growl for Windows, is that not the case? 
I don't see anything about it on http://growl.info

Original comment by [email protected] on 9 Sep 2010 at 12:54

[GoogleCodeExporter]

Well, FML.  GNTP has been "slated for the 1.3 release" for almost a year now.

Ah well, even though it's completely low on the list now, I'm politely 
requesting the minimalist approach here.  If you are smart, your WiFi is 
encrypted, and who has a firewall on their internal home network blocking TCP 
between their laptop and phone.

Original comment by [email protected] on 9 Sep 2010 at 1:41

[GoogleCodeExporter]

I'll take the feature request, but I won't promise to do it right now (let's 
see if GNTP comes out in Mac Growl anytime soon).

Original comment by [email protected] on 9 Sep 2010 at 1:52

• Changed state: Accepted
• Added labels: Component-Communication, OpSys-Android, Priority-Low

[GoogleCodeExporter]

Minimalist is great, but some of what we're talking about here make this 
attractive:  1) Pairing or limiting alerts specific machine(s) is important, 
even with home networks.  On my home network there are three of us, and a dozen 
devices using growl.  Not all of them need or want to see notifications from my 
phone.  In the office environment, there are several of this running this app, 
so it becomes even more important for both confusion and privacy reasons.  2) 
Bluetooth is important because in some locations (client sites, some offices) 
wifi use for a phone is not an option, regardless of whether there are privacy 
concerns.  

While in a perfect world, the receiver would only require growl, if the only 
way to deliver features is an app on the receiver, it's an acceptable trade-off 
to have to run that app.  

Original comment by [email protected] on 10 Sep 2010 at 7:55

[GoogleCodeExporter]

GNTP is actually slated for Growl's 2.0 release, and being that Peter and I are 
working on Growl in our spare time, we're looking at December at the earliest 
for the first beta.

Original comment by [email protected] on 10 Sep 2010 at 9:10