On Thu, May 26, 2011 at 1:08 PM, seahunt <[email protected]> wrote:
> On May 26, 12:39 pm, Christopher Forsythe <[email protected]> wrote: > > We're actually changing the updater to an in-app updater, which should > make > > this much less of an issue. However, it's a good idea to include this > > somewhere. > > > > Chris > > > > I read that you are planning to implement Sparkle. Here's a Sparkle > implementation request: I have lots of apps which use Sparkle for > updates, but the ones I keep on my system and continue to use are the > ones which give me a chance to save the downloaded update (no > surprise: I'm not a big fan of the Mac App Store). Some apps do that > by not cleaning up the temporary directory, some do it by implementing > an "Install and Relaunch" option. In the "Install and Relaunch" case, > the app can clean up after itself, but I can save the update before I > click the "Install and Relaunch" button. > > The benefit for us using sparkle is that we can just use their framework with little to no modification on our end. In other words, request this of sparkle. Chris -- 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.
