On 30 Sep 2009, at 10:39, Peter Hosey wrote:
> > On Sep 30, 2009, at 02:34:14, [email protected] wrote: >> I hadn't really paid much attention to GrowlSafari, as I don't >> really use it, but I've just noticed that it's changed to an app, >> presumably because of the 'no input manager loading in snow >> leopard'... >> Anyway, currently as far as I figure, it starts up and then it sits >> as a daemon process, waiting for safari sessions to add itself into >> or similar? > > More agent than daemon, but otherwise, yes, that's exactly what it > does. > >> this requires it to >> 1. sit, admittedly not doing much, around all the time, > > Not doing *anything*. The only time GrowlSafari actually takes up time > on the processor is when it launches and when another application > launches, and the only thing it does in the latter case is check > whether the newly-launched application is Safari and, if so, inject > into it. > > The rest of the time, GrowlSafari uses up no processor time and very > little memory. > >> The Chax iChat plugin (http://www.ksuther.com/chax/) has had to >> adapt similarly, but in this case, the application acts as a full- >> blown wrapper, so when I want to use iChat, I open Chax instead (and >> I register Chax as the default chat app, etc.) > > Yeah, what a hassle. And you can only have one of those—you couldn't > have GrowlSafari and another Safari-injector app if both apps did it > that way. > ah, good point. i thought you'd have a good reason for doing it your way... :) --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Growl Discuss" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [email protected] For more options, visit this group at http://groups.google.com/group/growldiscuss?hl=en -~----------~----~----~----~------~----~------~--~---
