GNTP 1.0 and GfW 2.0.9 questions about local icon image files, duration, multiple text lines

[ToddA]

Hi,

1. This post mentions the possibility of using a local path, and I'm wondering if this capability is supported? I don't know which document that post is quoting from. I'm interpreting it to mean that "Application-Icon:" (and maybe "Notification-Icon:"?) can specify a special URL to a file local to where GfW is running.

2. There are some notifications that I'd like to last a little longer than the default, but I'd like to be able to specify the duration when I send the GNTP packet. In GfW on the Applications pane there's a dropdown for the duration. How can I a) change the default duration that GfW uses and b) is there a way I'm not seeing to specify the duration in the GNTP packet?

3. Is it possible to force a text and/or title line to start a new line, something like "First line\rSecond Line"? I'm mainly sending GNTP packets from Linux using a shell script.

Kind regards,
Todd

[darrylo]

On Tuesday, April 30, 2013 11:48:52 PM UTC-7, ToddA wrote:

3. Is it possible to force a text and/or title line to start a new line, something like "First line\rSecond Line"? I'm mainly sending GNTP packets from Linux using a shell script.

While the title is a single line, just include newlines in the message (not carriage returns).  You can send pretty involved messages that way.

[briandu...@gmail.com]

1. Using a local file path is supported in GfW. You can use the file:/// syntax to specify the local path (ex: file:///c:/TEMP/image.png)
2. The amount of time a notification is displayed is controlled by the receiver (end user). As such, you cant specify the duration when sending the notification. As an end user, there is no global setting for duration - you have to modify it on an application-by-application (or individual notification type) basis.
3. As darrylo suggested in another reply, you can use newlines (\n) to indicate line breaks. Note that some displays limit the amount of text displayed based on how they are designed, but most displays should handle the \n character properly. 

--
You received this message because you are subscribed to the Google Groups "growl for windows" group.
To unsubscribe from this group and stop receiving emails from it, send an email to growl-for-wind...@googlegroups.com.
To post to this group, send email to growl-fo...@googlegroups.com.
Visit this group at http://groups.google.com/group/growl-for-windows?hl=en.
For more options, visit https://groups.google.com/groups/opt_out.
 
 

[ToddA]

Thanks, Darrylo and Brian, for getting back to me so quickly. I must say, playing... err... working with GfW is a lot of fun with the various Displays.

Would it be possible for you to update the spec at http://www.growlforwindows.com/gfw/help with the answers you've provided? In case it helps, I'm attaching "Growl for Windows.htm" with suggested changes. (Also, although the spec is very thorough, I find it to be somewhat "busy," making it difficult to quickly find what I'm looking for. Indentations would help, and I know that's probably something best done by CSS, but I don't know enough about CSS to contribute such changes like I'm doing with the attachment.)

Regarding the notification duration, I'm not sure I understand why the it isn't allowed to be specified in the notification itself, but sticky can be. In other words, what is the difference between:

     - notification setting sticky, and user clicking on it to make it go away
     - notification setting duration, and user clicking on it to make it go away (before the time expires)

I'm somewhat puzzled as to why sticky isn't strictly controlled by the user but the notification delay must be. Is there some risk in having the notification set the delay that I'm missing? (I'm not asking to be confrontational, just trying to understand.)

Here's why I'm asking about this: I'm attempting to automate an application's registration/configuration as much as possible so the user does not need to always tweak settings. I'd like to specify the notification duration as a reasonable out-of-the-box default when I register the app. I'm able to set everything else via REGISTER (including the icon graphics, which is a great feature!) and would like to do the duration as well.

[ToddA]

Sorry, that URL to the spec should be: http://www.growlforwindows.com/gfw/help/gntp.aspx

[Brian Dunnington]

Thanks for the feedback and updated GNTP help file. I will work on getting the changes added to the document. Just a note though: the newline characters are not universally ignored in Notification-Title nor accepted in Notification-Text. The text of each (including the newlines) is passed to the display as-is and each display handles it as they see fit. Some displays have vertically-expanding Title fields and allow longer text, while some truncate the title to fit within a predefined area.

As for why the duration is not able to be set via a GNTP header: there is no good reason =)  It was just that how long the notification stays on screen was initially thought to be more of a user-specified type of setting and not something the app would need/want to control. There is no harm in allowing it to be passed in since the user's setting will ultimately override it if they want it to (just like the Sticky pref), but it just wasnt considered at the time the spec was being hammered out.

[ToddA]

Hi Brian,

OK, that's good for me to know about the newlines. Could you add verbiage in the spec to the effect that it is dependant on the Display being used? That way if it doesn't work in some cases, I can let end-users know to contact the person who created the Display.

>As for why the duration is not able to be set via a GNTP header: there is no good reason =) 

I quite understand. :D Can you add this to the feature request list, perhaps for GNTP 1.1?