Just FYI, we've bee using a very recent (newer than 1.5b6) version of Sparkle in Sandvox and iMedia Browser over the last year and a half. The latest seems very solid. You can download it (without having to use Git) from its development home: http://github.com/andymatuschak/Sparkle
On Feb 16, 2010, at 5:51 AM, Jon Gotow wrote: > At 6:38 PM +0100 2/15/10, Uli Kusterer wrote: >> We simply provide an RSS item without a download, but with a >> sparkle:version tag (We extended Sparkle to allow for that, and >> AFAIR Andy merged that into his Github repository, otherwise find it >> in my Sparkle branch at http://www.github.com/uliwitness). It will >> then redirect you to the link specified in the RSS feed (with a >> "learn more" button) instead of downloading something. Just like any >> other version notification, they can click it away and ask to not be >> reminded. > > Thanks Uli - that's precisely the kind of idea I was looking for. > Great solution! I'm currently using the last "official" Sparkle > release, 1.5b6, so I assume the best course of action would be to > download the source from your branch? It's been tested (at least for > your use) whereas the main Sparkle repository is in an unknown state. > >> We just put a note in the notification in what timespan you're >> eligible for a free upgrade, and put a link to that on the "Learn >> More" page. People who only recently bought the previous version and >> are eligible for a free upgrade thus get the same page, but can >> click that link to get the freebie. > > Sounds great! I'm going to go a step further and put an extra key in > the appcast for the upgrade grace period - I can then switch the > behavior based on whether the person gets a free update or not (go > ahead and automatically update if they're getting it for free). > >> To actually download it, we have a custom URL scheme (that support >> can also use to hand out beta versions with select fixes, or easily >> let a user downgrade their version until an issue is resolved), >> which will add a CGI parameter to the URL and fetch a particular >> version explicitly. > > Interesting - what does the custom URL scheme get you that an url to > the cgi with an embedded parameter does not?
