API to show Preferences panel

[GoogleCodeExporter]

What feature or enhancement do you propose?
A method to show the Growl preferences panel.

What problem does it solve/What benefit does it provide?
Now that the preference pane is gone, launching into the Growl preferences is 
trickier. First you have to find the right application and then you have to 
launch it and activate if it's not already running, since the preferences 
window won't come up otherwise.

A method to show the preferences would be helpful to include for use in other 
applications' configuration. Chris mentions that Growl has enough information 
that it should be able to launch directly into the app's entry in the 
preferences (its notifications) and while that would be nice, it's not 
completely necessary. If this is implemented, maybe there will need to be two 
methods to allow just bringing up the preferences.

Original issue reported on code.google.com by woot...@gmail.com on 17 Oct 2011 at 10:05

[GoogleCodeExporter]

Opening to the application settings was more an idea than "has enough 
information that it should be able to", but it'd be neat.

Original comment by ch...@growl.info on 17 Oct 2011 at 10:06

[GoogleCodeExporter]

Fair enough, but it does have enough information for that.

Original comment by woot...@gmail.com on 17 Oct 2011 at 10:13

[GoogleCodeExporter]

not to be looked at prior to Growl 1.4.

Original comment by rarich...@gmail.com on 20 Oct 2011 at 5:34

• Added labels: Milestone-1.4

[GoogleCodeExporter]

Please take a look and evaluate this one when you get a chance.

Original comment by ch...@growl.info on 20 Oct 2011 at 5:35

[GoogleCodeExporter]

Original comment by ch...@growl.info on 20 Oct 2011 at 5:37

• Added labels: Product-SDK

[GoogleCodeExporter]

I agree this is useful for 1.4.  To folks new to Growl, the concept that you 
have to go into Growl to configure notifications for other apps gets confusing. 
 With the addition of Mist (where the configuration of whether or not to show 
notifications might be in the app or might be in Growl), this confusion is 
likely to increase.  The ability to pull up Growl from in an app would make it 
possible to have a 'Notifications' section of app settings which either can 
open Growl or can give you on/off toggles for Mist notifications.

Original comment by cerulean...@gmail.com on 20 Oct 2011 at 5:49

[GoogleCodeExporter]

Done.  Added a growl:// URL scheme to Growl, Growl now can launch to a specific 
app's preferences, or a specific display style, and added this to the framework 
(more features potentially coming, but this was a good start).
Relevant commits in default of the development repo are:
4f8243371a2a and 6a4352a285d6.
Tested in sandboxed Beephammer, and it works just fine.  

Original comment by dan...@growl.info on 3 Dec 2011 at 7:48

• Changed state: FixedInSource

[GoogleCodeExporter]

Awesome.

Original comment by woot...@gmail.com on 4 Dec 2011 at 11:21

[GoogleCodeExporter]

[deleted comment]

[GoogleCodeExporter]

Will there be a way through the framework to know if this scheme will work, so 
I can show the button only when it will actually open Growl?

Original comment by livings...@gmail.com on 4 Dec 2011 at 9:24

[GoogleCodeExporter]

In reply to comment 10, use NSWorkspace's -(NSURL 
*)URLForApplicationToOpenURL:(NSURL*)url method to see if Growl will respond, 
and act accordingly.

Some details on which particular URL endpoints are available would be nice. 
"Added this to the framework" makes it sound like they have methods for doing 
this automatically but I don't have access to that repository, so I can't tell.

Original comment by woot...@gmail.com on 7 Dec 2011 at 7:59

[GoogleCodeExporter]

A check to know if the growl:// is available has been added to the framework as 
well (and yes, it uses URLForApplicationToOpenURL), I just forgot to update 
this.

Original comment by dan...@growl.info on 7 Dec 2011 at 8:49