On 17.02.2010, at 01:36, Sean Dougall wrote: > I may be missing something, but why not just set up a separate > appcast? Is there any reason why your v1 users _would_ ever want to > find out about v2 releases? (Aside from a general sort of "hey, v2 is > available!" announcement, for which Sparkle doesn't quite seem like > the right venue to me.)
We do have separate feeds (in fact, we have a server-side switch), but you *want* your users to be aware of the new version. Sparkle provides a nice notification window already, which can contain arbitrary text and pictures, and it also provides a reliable mechanism for the user to turn off this notification. They already know the UI from previous updates, and they activated it, so they've told you they're interested. All of these, another solution would have to duplicate. If you just have an update that can forward them to your shop if the user voices interest in the paid upgrade (or disappears if the user isn't interested), and which also triggers the download and automatic install at the click of a link, that seems to be much more in the spirit of Sparkle for me. I'd be interested in hearing why you think Sparkle isn't the right venue here, and what you would do instead? > With a separate appcast, you could even continue releasing minor v1 > bugfixes if necessary, without worrying about breaking things for v2. Definitely. A paid upgrade should still leave older versions with the ability to get emergency/security updates etc. -- Uli Kusterer Sole Janitor http://www.the-void-software.com
