[Sparkle] SparklePlus -> Sparkle 1.5 transition

[Andy Matuschak]

It actually uses SUSendProfileInfo. Sorry about the confusion: I  
didn't really like the name "SUIncludeProfile." You're right, though— 
that's something to watch out for. If a Sparkle+ user wants to make a  
branch with migration code people can merge in, that'd probably be  
really useful.

As it stands, be aware that if you're moving from Sparkle+ to Sparkle  
1.5, it will just plain stop sending profiling information, and it  
won't ask the user for permission, because it's already past the point  
where it's asking the user things. You'll have to devise some solution  
to make things keep working.

- Andy Matuschak

On Jun 18, 2008, at 6:30 AM, Brian Webster wrote:

> I'm transitioning an app from SparklePlus over to Sparkle 1.5 and  
> came across a little gotcha.  SparklePlus used a key called  
> "SUIncludeProfile" to determine whether or not to send the user's  
> information, while Sparkle 1.5 uses "SUProfileInfo" instead.  So,  
> for users that opted in to including profile info in an earlier  
> version, Sparkle 1.5 won't automatically pick this up, since it's  
> stored in a different key.
>
> I'm not sure if this is something Sparkle 1.5 should handle itself,  
> or whether developers who used SparklePlus should just be warned  
> that they'll have to either reask the user or copy the old key to  
> the new key the first time they start up with the new version.  Any  
> thoughts?
>
> --
> Brian Webster
> bwebster at mac.com
> http://homepage.mac.com/bwebster/
>
> _______________________________________________
> Sparkle mailing list
> Sparkle at lists.andymatuschak.org
> http://lists.andymatuschak.org/listinfo.cgi/sparkle-andymatuschak.org

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.andymatuschak.org/pipermail/sparkle-andymatuschak.org/attachments/20080618/3c778fc9/attachment.htm>